Use GitHub's auto merge rather than Microsoft's. #17519

Closed
opened 2026-01-31 05:44:55 +00:00 by claunia · 1 comment
Owner

Originally created by @ChaseKnowlden on GitHub (May 19, 2022).

Description of the new feature/enhancement

Switch to GitHub's auto merge.

Proposed technical implementation details (optional)

No longer use Microsoft's Internal Auto merge.

Originally created by @ChaseKnowlden on GitHub (May 19, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Switch to GitHub's auto merge. # Proposed technical implementation details (optional) No longer use Microsoft's Internal Auto merge.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 05:44:55 +00:00
Author
Owner

@DHowett commented on GitHub (May 19, 2022):

Hey @ChaseKnowlden! Thanks for the request! For right now, we actually prefer Microsoft's automerge for two key reasons:

  • We can add somebody as a "required" reviewer by asking the bot to "make sure xxx signs off"
  • We can set a time limit before the automatic merge happens, to give reviewers a "last chance" to air any grievances by asking the bot to "merge this in xxx minutes/hours/days"

Until GitHub's automatic merge feature supports required/optional reviewers at a minimum, we're not likely to switch. But don't worry -- we've been asking them for that feature!

@DHowett commented on GitHub (May 19, 2022): Hey @ChaseKnowlden! Thanks for the request! For right now, we actually prefer Microsoft's automerge for two key reasons: * We can add somebody as a "required" reviewer by asking the bot to "make sure xxx signs off" * We can set a time limit before the automatic merge happens, to give reviewers a "last chance" to air any grievances by asking the bot to "merge this in xxx minutes/hours/days" Until GitHub's automatic merge feature supports required/optional reviewers at a minimum, we're not likely to switch. But don't worry -- we've been asking them for that feature!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17519