One of the more common requests we hear from Lead Developer and Project Managers is to be notified if a pull request seems to be stuck in a state that is pending merge. GitClear offers the following options to be notified when this occurs:

open_in_new

These settings can be adjusted by visiting Settings -> Pull request targets. Thresholds are configured on a per-repo basis, so if you visit settings on an organization or entity page, all repos within that resource will be updated.

linkMaximum Diff Delta

If this value is set, then pull requests present on the Pull Requests -> PR List tab will show how much each pull request went over or under the Diff Delta threshold. We recommend striving to keep most pull requests lower than 500-1000 Diff Delta. Since the average developer tallies around 100 Diff Delta per day, it's usually undesirable to ask a reviewer to review more than 10 days of work.

linkMaximum Comment Count

When this value is set, then pull requests present on the Pull Requests -> PR List tab will show how much each pull request went over or under your target comment threshold. In general, less than 25 comments is a good sign that the team is being effective at submitting easy-to-digest PRs.

linkMaximum Business Days Open

When this value is set, if a pull request has remained open for this many business days (weekdays excluding US federal holidays) will

Depending on how you have configured your notification settings, you can receive an email when this notification is triggered, or just see the notification when you log into GitClear.

linkMaximum Business Days Between Activity

Some managers are fine with long-running PRs (to a point), but they would like to know if the train of progress for a PR gets paused longer than a particular threshold. This setting allows one to configure their "Languishing Pull Request" notification (as above, configurable from the Highlights page) to be triggered when neither a commit nor a comment has been left for the given number of business days.