Handle GitHub response in auto-merge infra: "Pull request is not in the correct state to enable auto-merge"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
Recently I saw Pull request is not in the correct state to enable auto-merge in two places:
- https://dev.azure.com/dnceng/internal/_build/results?buildId=1537329&view=logs&j=dcac29c3-db0c-5aab-54f3-72ba43a49a08&t=1739381a-3424-591d-a559-75725716cd04&l=78
https://github.com/microsoft/go-images/pull/38 - https://dev.azure.com/dnceng/internal/_build/results?buildId=1535469&view=logs&j=4a0cec82-aaa7-5c07-9c1e-30cc88945a51&t=d35104de-7d40-5aa7-a628-491fd52b294b&l=565
https://github.com/microsoft/go/pull/341
My guess is that the PR was mergeable at the time, so auto-merge couldn't be queued up. But, I'm not sure why it wasn't enabled when the PR first got submitted, and there could be a completely different reason anyway.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the two Azure DevOps log links and their corresponding pull requests, microsoft/go-images#38 and microsoft/go#341, to determine when GitHub returned the auto-merge state error. Trace the auto-merge handling in this repository; done means the identified response is handled appropriately without failing the infrastructure workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github, go
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100