This feature was announced recently:
Apparently, it needs to be manually activated. Does anyone have any concern or you think we should go forward an activate the feature?
2 Likes
Will it change the commit message for us? (the “#” to “GH-”)
I would suggest continue using our automerge, which also respects the “awaiting merge” and “do-not-merge” labels, in addition to what Ethan said.
2 Likes
Will it change the commit message for us? (the “#” to “GH-”)
Not AFAIK. You still need to manually write the commit message (the same as when you merge normally). The advantage is not having to wait for CI, so in that sense is basically the “automerge” label without some features, and the main difference is that you don’t need to edit the PR message to configure the final commit.
1 Like
This has long been the #1 reason why I chose GitLab for my personal projects, so I’m really glad to see GitHub add support for this. That said, our bots have become more sophisticated and tailored to CPython’s workflow, as @Mariatta points out (huge kudos for that!). So I’m less inclined to desperately want it for CPython these days.
1 Like