-
Notifications
You must be signed in to change notification settings - Fork 565
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
Auto merge patch dependency updates #10333
Conversation
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.
merging...NOT!
3170c75
to
429a22a
Compare
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.
bors merge
🔒 Permission denied Existing reviewers: click here to make github-actions[bot] a reviewer |
So all good, but it seems the GitHub bot is not an approved review ;) |
For testing, see this run: https://github.com/camunda/zeebe/actions/runs/3045213733/jobs/4906497130 |
931150c
to
6d6a652
Compare
After merging, we would simply add the GitHub actions bot to the bors reviewers. If that's not desirable, we can use a PAT, but I can't see a reason why it won't be desirable. |
One last thing, I wasn't sure how to test the dependabot part without a dependabot PR, so we will find out on the first dependabot PR. |
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 👍
👏 Nice work @npepinpe 🚀 I'm excited to see this work
# Once we're using the merge queue feature, I think we can simplify this workflow a lot by relying | ||
# on dependabot merging PRs via its commands, as it will always wait for checks to be green before | ||
# merging. |
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.
👍 Nice
- uses: actions/checkout@v3 | ||
- id: metadata | ||
name: Fetch dependency metadata | ||
if: false |
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.
❓ if: false
, so this step is always skipped? If so, please clean it up.
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.
No, that's a left over for testing, my bad 🙈
Adds a workflow which runs whenever a PR is opened, reopened, marked as ready for review (so going from draft to ready), and updated (synchronized). The latter is to allow things such as `@dependabot rebase` to trigger this workflow. This workflow runs only if the author of the PR is dependabot, and if the repository is `camunda/zeebe`. It will only merge patch updates for now, but it could be updated to merge any kind of updates.
6d6a652
to
3c81194
Compare
bors merge |
10333: Auto merge patch dependency updates r=npepinpe a=npepinpe ## Description This PR adds a workflow which runs on every dependabot PRs, and will automatically merge the PR iff the checks pass, and it is a patch version (according to dependabot). Merging is still done via bors. The workflow is made of three steps: checking the dependabot metadata (used to determine the type of updates, e.g. patch, minor, etc.), waiting for specific checks to pass, then approving the PR with a `bors merge` comment (triggering the merge). If bors fails to merge, or checks fail, then manual action is still required. ## Related issues closes #10295 Co-authored-by: Nicolas Pepin-Perreault <nicolas.pepin-perreault@camunda.com>
Timed out. |
Nice to see it in action @npepinpe 🚀 |
Description
This PR adds a workflow which runs on every dependabot PRs, and will automatically merge the PR iff the checks pass, and it is a patch version (according to dependabot). Merging is still done via bors.
The workflow is made of three steps: checking the dependabot metadata (used to determine the type of updates, e.g. patch, minor, etc.), waiting for specific checks to pass, then approving the PR with a
bors merge
comment (triggering the merge).If bors fails to merge, or checks fail, then manual action is still required.
Related issues
closes #10295
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Please refer to our review guidelines.