-
Notifications
You must be signed in to change notification settings - Fork 69
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
Allow auto merge binding PRs #988
Conversation
binding-refs |
99e68cd
to
a70d0ee
Compare
489cdf1
to
d098fb9
Compare
b5a7ec6
to
f73342e
Compare
Most of the workflow is tested, and works fine. See https://github.com/mmtk/mmtk-core/actions/runs/6556991187. The workflows can update the mmtk dependency and turn on auto merging in the testing PR in OpenJDK (mmtk/mmtk-openjdk#254). One thing that is not tested yet is the merge commit hash. It is acquired with |
I think the current approach may not work if a mmtk-core PR is opened from a fork. The workflow needs to access |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some problems in the Python script replace-mmtk-dep.py
that should be changed.
This reverts commit db2e4b4.
I changed the workflow trigger. It should be fine now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I changed the way how to update the lock file. It now uses I don't plan to make any further changes to the PR unless requested. |
This PR updates mmtk-core to mmtk/mmtk-core#988. Once mmtk/mmtk-core#988 is merged, this PR should be updated to the new mmtk-core commit, and will be auto merged (if all the requirements for auto merging is met). --------- Co-authored-by: mmtkgc-bot <[email protected]>
We saw the auto merging workflow (added in #988) failed in https://github.com/mmtk/mmtk-core/actions/runs/6587030083/job/17896533403. The error message was `GraphQL: Head branch is out of date. Review and try the merge again. (mergePullRequest)`. It is likely caused by the issue https://github.com/orgs/community/discussions/24462: When a PR gets updated, Github has a process to determine if the PR is mergable. If we attempt to enable auto merge before the process is done, the merge will fail with the error message above. This PR adds a delay and retry for enabling auto merging.
This PR allows auto merging related binding PRs once the mmtk-core PR is merged. It also adds some docs for MMTk team about merging process. The PR closes #205.