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:install command 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.
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.