-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Pinning specific commits in a GH repo #62
Comments
Sure, why not. One way I could see to handle this:
My only worry is that this terminology could be confusing due to the double meaning of "pinning". Not sure how else to call it though An alternative would be to allow specifying which pins to skip while updating. Currently we can say |
My use case is to prevent updating inputs when I know they're broken after a certain rev, i.e. I'd pin to the last known working rev. I would lean towards the first option, since it would:
I do see the issue about calling it a "pin", though 😕 |
How about "freeze"/"frozen"? |
Yes, I think that makes sense. |
@eclairevoyant mind having a look at #78 and testing it? |
To add a GH source at a specific commit is explained as
In my case, I'd like to keep that source pinned to
<rev>
even after runningnpins update
. Is this possible?The text was updated successfully, but these errors were encountered: