Skip to content
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

Automate dependabot merges #202

Open
haydentherapper opened this issue Jan 3, 2023 · 2 comments
Open

Automate dependabot merges #202

haydentherapper opened this issue Jan 3, 2023 · 2 comments
Assignees

Comments

@haydentherapper
Copy link
Contributor

I think the vast majority, if not all, dependabot PRs are merged once tests pass. This is manual, and while it's not that much of a burden, I think we can automate this. See https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions#enable-auto-merge-on-a-pull-request for instructions on how to set this up.

When there's a major Go version update, I think we have to do something manually too, so maybe we don't merge those automatically.

I'm also not sure if we would need to update tests that are required for each repo, or if branch protection should limit merging if any test, required or not, fails.

I'd suggest this be enabled for the larger repos (Rekor, Fulcio, Cosign), and for others, maintainers can decide if they want to enable it or not.

cc @cpanato - Thoughts?

@cpanato cpanato self-assigned this Jan 4, 2023
@cpanato
Copy link
Member

cpanato commented Jan 4, 2023

This only enables the automerge feature; it does not merge it.
I agree to enable that for dependabot PRs.
Let me do that for the main repos

@cpanato
Copy link
Member

cpanato commented Jan 9, 2023

lets try in the timestamp first and then replicate to others

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants