Open mattmc3 opened 2 years ago
Are there any blockers to this feature being implemented? I'd like to help, if possible
No blockers - I've always thought of it as a pretty easy feature. I haven't done it yet because there hasn't been a lot of interest in it before now, and I just need some volunteers to test it.
My take on implementing the feature is this:
pin:SHA
annotation that tells antidote which commit SHA you want for your plugins.pin
subcommand like: antidote pin [-r|--remove] [<PLUGIN>] [<SHA>]
. This lets you pin (or unpin) a plugin (or all plugins) to either a specified SHA or whatever is currentantidote update
respects pinning and is a no-op for pinned reposantidote update
to unpin and then re-pin for a updates (a --force flag??)Any other relevant features you'd like me to consider as part of this feature?
Adding a layer that could convert tags to commit SHAs, as I have a few plugins that I version using tags. I'd make it so that the pin annotation would support pin:SHA|TAG
Per https://github.com/getantibody/antibody/issues/386: