Automatically decline inactive pull requests
Bitbucket Data Center can automatically decline pull requests that are inactive, reducing the number of pull requests in the list that can add up. For example, if an older pull request has not had any activity (like commits, comments or approvals) in a set amount of time, it will be declined. By default, the option is on and set to 4 weeks. This period of inactivity can be overwritten for projects and repositories.
On this page:
Automatically decline inactive pull requests for all repositories in a project
To configure the automatic declining of inactive pull requests in a project:
Select Project settings > Auto-decline.
Select the Auto-decline pull requests check-box to enable it.
Set the amount of time before a pull request will be automatically declined from 1, 2, 4, 8, or 12 weeks.
Select Save.
Automatically decline inactive pull requests for a repository
Configuring this setting at the repository level, will override the setting for it at the project level.
To configure the automatic declining of inactive pull requests in a single repository:
Select Repository settings > Auto-decline.
By default, settings are inherited from the project settings.
Select Use custom settings.
Select the Auto-decline pull requests check-box to enable it.
Set the amount of time before a pull request will be automatically declined from 1, 2, 4, 8, or 12 weeks.
Select Save.
Once the configuration is saved, inactive pull requests will become declined by the Bitbucket system user. This will add a comment indicating that the reason for the decline is due to inactivity.
Modify the global default
You can control the global default behavior for the auto-decline pull requests setting with the following properties:
pullrequest.auto.decline.settings.global.enabled- controls whether or not auto-decline setting is enabled by default for all repositories.pullrequest.auto.decline.settings.global.inactivityWeeks- sets the global default inactivity period.
For a complete list of properties that can be used to control behavior in Bitbucket, see Configuration properties.