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

How to handle (future) Depdenabot updates? #3028

Closed
clin1234 opened this issue Jun 27, 2023 · 1 comment
Closed

How to handle (future) Depdenabot updates? #3028

clin1234 opened this issue Jun 27, 2023 · 1 comment
Labels
Build Automation Enhancement Areas for improvement

Comments

@clin1234
Copy link
Contributor

I've just opened a pull request #3027 to bump a few dependencies. Far as I can tell, the GitHub Actions pass on both my fork and will soon do so upstream.

So, what's the policy from now on? Let upstream bump them automatically, or request manual merges from forks?

@clin1234 clin1234 added the Enhancement Areas for improvement label Jun 27, 2023
@christophwille
Copy link
Member

Those deps were manually updated quite some time ago - and the "policy" regarding GH actions is more or less: we own them, we update them.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Build Automation Enhancement Areas for improvement
Projects
None yet
Development

No branches or pull requests

2 participants