Automatically update the list of packages with versions during extract + improve install #430
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
muzzwood
force-pushed
the
better-packages
branch
from
ca65fb9
to
1430108
Compare
muzzwood
force-pushed
the
better-packages
branch
from
ce8db10
to
8ea7544
Compare
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.
What does it do ?
By default, update the .gitify file with installed packages and provider information when extracting. This makes it so the list of packages should be up-to-date. This can be opted out of with
--no-packages.Also update the
package:installcommand to skip installing if an exact version match or a higher version of a package is already installed. This speeds it up a lot when there is nothing to update.Why is it needed ?
Package support is kinda flaky in Gitify. This helps make a more complete workflow possible.
Related issue(s)/PR(s)
#157
#357
#262
Fixes #108
There are a couple of outstanding PRs that might conflict with this. I'd suggest sorting those out first, and then I'll happily update this one.
Specifically, #417 adds the ability to use a different config file, so this will need to be updated to write to the provided config file instead of the hardcoded one.