Tag github

 Reply

We've found it to work quite well on my team, as it allows folks to see things they're not necessarily involved in, and actively seeks out their thoughts, as well as not leaving it up to the PR raiser to decide who

(Although we're currently using the "round Robin" approach)

It also doesn't mean others can't review

 Reply

Hmm I'll have to try it but I thought rebase-merge was the same as a --no-ff merge

 Reply

You can also do this with a "rebase merge" on GitHub, and yep would recommend it if you don't want merge commits. I'd generally say keep them, but amend the titles to be ie PR title

 Reply

We only have this set up in a few places as it's not possible to do it org-level as you say, or configure it via the API https://github.community/t/support-autolink-reference-configuration-in-the-api/14614/

 Like

 Like

 Reply

I'm sure I've seen this when you look at the merge commit, or commits on the main branch, if the repo uses tagging - it shows all tags applicable, so you have to do some thinking to find the first

 Note

I'm really surprised #github has only got "merge when this PR succeeds" - at work we've got an internal bot to do this for us but it'll be great when it's part of the platform!

 Like

 Like