DevSensei Auto-Merge allows you to merge pull request that do not require feedback from coworkers but still need to go through the CI checks. We call these pull requests SHOW in reference the Ship/Show/Ask principle.
In order to let pull requests be auto-merged, do the following:
-
Add [SHOW] in front of your pull request title. Example:
[SHOW] Update vulnerable dependencies. The app will pick the Pull Request to be auto-merged. -
As soon as all the following conditions are fulfilled, the pull request is merged automatically:
-
All builds ran successfully
-
No reviewer requested changes
-
No task is left open
-
No enforced merge check is failing
-
-
The pull request is merged shortly after all conditions are met.
Limitation: Branch restrictions not supported
Due to how apps can merge PRs in Bitbucket Cloud by Atlassian, the app can not merge, if Branch restrictions are active for the destination branch.
Here is a quick recap of how pull requests can be categorized in ASK and SHOW pull requests.
-
Ask pull requests: You want feedback and discussions on these pull requests. You only want to merge these after there was enough time for discussion and reviewing changes. Examples:
-
Adding a new feature
-
Changing how a feature work
-
Major refactoring
-
-
Show pull request: You want to show what was done, but otherwise go ahead with the change. You want the pull request as a record, to let the CI check the pull request, and maybe to add comments after the fact. Otherwise, you want to merge the changes without waiting for feedback from coworkers. Examples:
-
Fixing a typo or spelling mistake
-
Small refactoring like renaming a badly named function
-
A bugfix you already discussed with the team or paired programmed on
-
Increasing a dependency's minor version
-