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

Make dependabot updates to a different target-branch #2836

Closed
ashleysommer opened this issue Jul 24, 2024 · 2 comments
Closed

Make dependabot updates to a different target-branch #2836

ashleysommer opened this issue Jul 24, 2024 · 2 comments

Comments

@ashleysommer
Copy link
Contributor

My intention is to create a new "bot-updates" branch for dependabot to target its PRs.
Related to #2835

This means we can merge multiple updates to the same branch while ignoring CI failures, we will not worry about lockfile problems. This means we don't block other PRs from running CI due to bad lockfile issues.
We can periodically create a new working lockfile from the bot-updates branch and push the new pyproject.toml and matching working poetry.lock file from that branch into main when we are ready.

Thoughts?

@nicholascar
Copy link
Member

Any automation or grouping of the small updates is good since we do need to roll them in, but we don't have to have them all hanging around all the time individually.

Are all dependabot and similar PRs flagged in such a way - labels etc. - that we could write a GH Action to deal with them automatically whether on the main branch or another?

@nicholascar
Copy link
Member

This Issue has been bypassed by getting a handle on dependabot PRs generally

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