-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition to GitHub-native auto-merge feature #1289
Labels
Central-EngSys
This issue is owned by the Engineering System team.
EngSys
This issue is impacting the engineering system.
Comments
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Dec 17, 2020
weshaggard
added
Central-EngSys
This issue is owned by the Engineering System team.
EngSys
This issue is impacting the engineering system.
labels
Jan 4, 2021
kurtzeborn
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jan 4, 2021
We should use the |
I've been testing some of this in the azure-sdk repo at https://github.com/Azure/azure-sdk/blob/main/eng/pipelines/version-updater.yml#L91-L97 |
Closing in favor of Azure/azure-sdk#5832 |
github-project-automation
bot
moved this from 📋 Backlog
to 🎊 Closed
in Azure SDK EngSys 🚢🎉
Jun 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Central-EngSys
This issue is owned by the Engineering System team.
EngSys
This issue is impacting the engineering system.
Currently we make use of fabric bot to auto-merge PRs which have the auto merge label once all the checks have passed in the PR is approved. GitHub recently rolled out a native automerge feature so we should plan on moving to that. This work will involve:
It isn't clear at this point whether automerge settings are exposed on the REST API. This would probably be the initial investigation.
The text was updated successfully, but these errors were encountered: