Pull request data quality
Exclude irrelevant pull requests from all Swarmia metrics to filter out noise and get better insights.
Last updated
Was this helpful?
Exclude irrelevant pull requests from all Swarmia metrics to filter out noise and get better insights.
Last updated
Was this helpful?
Old open pull requests can make pull request cycle time metrics difficult to interpret. Excluding pull requests provides you the option to hide old and stale pull requests in Swarmia. This is especially useful for you to start focusing on improving ways of working when adopting Swarmia without letting the burden of the past get in your way.
If your team has pull requests with no activity since the last 30 days Swarmia prompts you the option to exclude them in bulk on the .
Note that this features doesn't do anything to pull requests on GitHub, and you can continue working on excluded pull requests at any time. We recommend starting with the bulk exclusion, as you can include any excluded pull requests back into metrics later, if you so choose.
Not all irrelevant pull requests are more than 30 days old. To give you the flexibility of configuration, we allow excluding any individual pull request from your metrics.
The filters can be defined on organization level with multiple filter types and combinations
Branch or title name prefix (E.g "suggestion:")
Draft status
If you are for example exploring solutions with draft PRs, you can automatically exclude them.
Pull request labels
Repository
The exclusion can be also limited to match only certain repositories within your organization
Pull request status
The pull request details pop-up shows if the pull request has been automatically excluded.
You can define pull request exclusion filters for certain type of work to avoid irrelevant exceptions and alerts. This type of work might include draft, revert, or release pull requests. You can configure the filters in the pull requests .
