Skip to main content
After installing the Sweetr GitHub App, we run an initial sync that pulls in your organization’s repositories, pull requests, code reviews, and teams. This guide walks you through what was set up automatically and what you should review.

​
Setup Teams

Sweetr imported your GitHub teams and their members during the initial sync.
This is a one-time import.If you change teams in GitHub later, those changes won’t show up in Sweetr.You’ll need to edit teams directly in Sweetr going forward.

​
What to do

1

Review your teams

Check the Teams page. Make sure the imported teams match your current org structure and remove any that are outdated.
2

Adjust membership

Add or remove members as needed. See Teams for details on roles and management.
3

Explore team insights

Once your teams look right, you’re free to explore team-scoped views like Work Log and Work in Progress.

​
Setup DORA metrics

To calculate DORA metrics, Sweetr needs to know about your applications, deployments, and incidents.

Applications

Sweetr created an application for each of your repositories during the initial sync. An application is a deployable unit that connects a repository to its deployments and environments.
Sweetr supports monorepos but can’t detect them on initial sync.If you have monorepos, split the auto-created application into separate applications and map each to a subdirectory. This way pull requests get linked to the right application.

Deployments

Every auto-created application is pre-configured to consider the merge of a Pull Request as a deployment, so you have DORA metrics from day one.This is often inaccurate as many companies deploy multiple PRs at once. You should switch to the API Webhook trigger for full data accuracy.
Tip: After creating applications, you can go to Settings > Workspace and click “Resync all historical data” to backfill deployments from previously merged PRs.

Incidents

Incidents are production issues caused by a deployment. They feed into Change Failure Rate and Mean Time to Recovery.Sweetr has Incident Detection enabled by default. It creates incidents when it spots rollbacks, hotfixes, or reverts. You can also create them manually.

​
What to do

1

Review your applications

Go to Applications and check the auto-created list. If you have monorepos, split them into separate applications per service.
2

Tweak incident detection (optional)

The Incident Detection automation is already running. If your team uses specific branch names or PR labels for hotfixes, customize the patterns there. Then check Incidents to make sure the auto-detected ones look right.
3

Check your DORA dashboard

Go to DORA Metrics to see how your team is doing.

​
Inviting teammates

Share the workspace URL with your team. Anyone in your GitHub organization will auto-join when they log in with their GitHub account.