You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My project wishes a "linear history" in Git for the reason described in this article. Therefore, they have set BitBucket to allows only the Fast-forward only merge strategy, which rejects a Pull Request if the source branch is out of date with the target branch. To fix the out-of-date problem you would have to rebase in Git to rewind your changes to the top of the history and do a forced push on the source branch. Usually this goes without conflicts, and with no soure code changes, but the gocd-build-github-pull-requests plugin will do a rebuild anyway. When combined with the GoCd build status notifier plugin, which is configured to require 1 successful build before a PR can be merged, this can greatly increase the time required for a successful merge.
Therefore, I would like to request an option to disable building PRs when they change but there were no actual source code changes. E.g. the Bitbucket Server Auto Unapprove Plugin already works in a similar way, that, you can rewind to top without automatically removing the approved statuses of reviewers.
I know that potentially every successful merge or rebase can do functional breakage in the build, but in our experience the probability of that is too low, thus not worth it for us, and we already have a CI/CD build that triggers after changes in the target branch.
This feature request may need changes in the notifier plugin as well, I don't know for sure.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
@rkrisztian Would you be interested in sending a PR for this change? You might want to add a configuration in the plugin and check for it in this method. This was the default behavior of the plugin, but the community wanted to merge commits with no source file changes as well. So this can be an opt-in feature which can be enabled as seem fit for use-cases described above.
My project wishes a "linear history" in Git for the reason described in this article. Therefore, they have set BitBucket to allows only the Fast-forward only merge strategy, which rejects a Pull Request if the source branch is out of date with the target branch. To fix the out-of-date problem you would have to rebase in Git to rewind your changes to the top of the history and do a forced push on the source branch. Usually this goes without conflicts, and with no soure code changes, but the gocd-build-github-pull-requests plugin will do a rebuild anyway. When combined with the GoCd build status notifier plugin, which is configured to require 1 successful build before a PR can be merged, this can greatly increase the time required for a successful merge.
Therefore, I would like to request an option to disable building PRs when they change but there were no actual source code changes. E.g. the Bitbucket Server Auto Unapprove Plugin already works in a similar way, that, you can rewind to top without automatically removing the approved statuses of reviewers.
I know that potentially every successful merge or rebase can do functional breakage in the build, but in our experience the probability of that is too low, thus not worth it for us, and we already have a CI/CD build that triggers after changes in the target branch.
This feature request may need changes in the notifier plugin as well, I don't know for sure.
Thanks in advance.
The text was updated successfully, but these errors were encountered: