Handle updating unstable packages #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a few packages that track latest commit of a branch rather than a version -- typically I handle that with the
--version=branchargument tonix-update. To handle those as part of the action, I added a check against a packageversionparameter -- if it contains the wordunstable(which is whatnix-updateand the nixpkgs versioning convention use to denote packages like this), then it does--version=branch; otherwise, it does--version=stable(which should be the default mode).I also bumped
create-pull-requestas I ran into this issue running the action if an PR from a previous run was still open.