-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Policy Service sometimes doesn’t enable automerge #142854
Labels
Area-Bots
These issues are related to the bots assisting with automation
Area-External
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Needs-Attention
This work item needs to be reviewed by a member of the core team.
Comments
microsoft-github-policy-service
bot
added
Needs-Triage
This work item needs to be triaged by a member of the core team.
Area-External
Area-Bots
These issues are related to the bots assisting with automation
Needs-Attention
This work item needs to be reviewed by a member of the core team.
Issue-Bug
It either shouldn't be doing this or needs an investigation.
and removed
Needs-Triage
This work item needs to be triaged by a member of the core team.
labels
Mar 7, 2024
This was referenced Mar 7, 2024
Trenly
changed the title
Policy Service soometimes doesn’t enable automerge
Policy Service sometimes doesn’t enable automerge
Mar 7, 2024
This was referenced Mar 7, 2024
This was referenced Mar 8, 2024
6 tasks
7 tasks
7 tasks
7 tasks
This was referenced Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Bots
These issues are related to the bots assisting with automation
Area-External
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Needs-Attention
This work item needs to be reviewed by a member of the core team.
Sometimes Auto-Merge isn’t being enabled and it isn’t clear why. The triggers are working for most PRs, but a few are getting into a state which require a manual merge. I expect this is an issue with the policy service itself either running into rate limits or internal errors
The text was updated successfully, but these errors were encountered: