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.

Sign up for GitHub

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

Jump to bottom

CI: flake.lock update job should update the existing PR if an unmerged one exists #467

Open
mrjones2014 opened this issue May 23, 2024 · 0 comments · May be fixed by #468
Open

CI: flake.lock update job should update the existing PR if an unmerged one exists #467

mrjones2014 opened this issue May 23, 2024 · 0 comments · May be fixed by #468
Assignees
@mrjones2014
Labels
bug Something isn't working flake.lock automation

Comments

@mrjones2014
Copy link
Member

That is, if we haven't merged a flake.lock PR by the time the job runs again, the job should push to the existing branch, updating the unmerged PR with the latest flake.lock changes.

Currently it fails because the branch already exists; instead of failing, it should push to the existing branch.
@mrjones2014 mrjones2014 added bug Something isn't working flake.lock automation labels May 23, 2024
@mrjones2014 mrjones2014 self-assigned this May 23, 2024
@mrjones2014 mrjones2014 linked a pull request May 24, 2024 that will close this issue
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrjones2014 mrjones2014

Labels
bug Something isn't working flake.lock automation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(ci): Update existing flake.lock PR if it exists already 1Password/shell-plugins
1 participant
@mrjones2014