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
Hi! Thanks for sharing and maintaining this project! 🙌
Sometimes we want to use different merge methods, based on the commits to a branch. It would be nice if we could control it per branch - e.g. by commenting on a PR with "bulldozer squash", which would have bulldozer do a squash merge.
It's not obvious from our docs, but I think this actually works today. I created a test project with the following configuration and it worked as you described. Bulldozer triggered when I left a comment (or added a label) and it used the appropriate merge method for that trigger to merge the PR:
Please try it out and let me know if this is what you were looking for. Note that unlike the "standard" trigger block, when used in merge_method, all of the triggers much match to select a method. That's why I had to duplicate the definitions for labels and comments, instead of combining them in to a single rule.
Hi! Thanks for sharing and maintaining this project! 🙌
Sometimes we want to use different merge methods, based on the commits to a branch. It would be nice if we could control it per branch - e.g. by commenting on a PR with "bulldozer squash", which would have bulldozer do a squash merge.
Would this behavior be desired? It could of course be completely disabled by not configuring it.
The text was updated successfully, but these errors were encountered: