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

update-flake-dependencies job fails if the previous automated PR isn't merged #452

Closed
mrjones2014 opened this issue Apr 12, 2024 · 0 comments · Fixed by #456
Closed

update-flake-dependencies job fails if the previous automated PR isn't merged #452

mrjones2014 opened this issue Apr 12, 2024 · 0 comments · Fixed by #456
Assignees
@mrjones2014

Comments

@mrjones2014
Copy link
Member

What does it concern?

The Makefile commands and tooling

Goal or desired behavior

The CI job to update the flake.lock should ideally close the previous PR if it hasn't been merged yet and open a new one.

Current behavior

Currently it just fails because the branch name is already in use (by the previous PR).

Relevant log output

No response

op CLI version

No response

shell-plugins local ref

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrjones2014 mrjones2014

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(ci): Auto-add one approval to automated flake.lock PRs 1Password/shell-plugins
1 participant
@mrjones2014