- Notifications
You must be signed in to change notification settings - Fork912
ci: fix cla and dependabot notifications jobs#16343
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
types: | ||
- opened | ||
- closed | ||
- synchronize | ||
- labeled | ||
- unlabeled | ||
- opened |
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.
removed the duplicate from L8
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Switch `release-labels` job trigger to `pull_request_target` and refine`dependabot` automerge conditions by verifying `actor_id`. Enhancelogging for approval and merge steps to provide better visibility.
e37b7fc
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
When we merge a PR programmatically using
gh pr merge --auto --squash,
the Github auto handles the merge after all checks are passed. So, apull_request
event does not get triggered, and a merge commit is pushed tomain
bygithub-actions[bot].
This change handles that case.I also extracted all dependable logic to a separate workflow for better control and restored the original state of
contrib.yaml
so that cla can work as expected for Community PRs.