-
Notifications
You must be signed in to change notification settings - Fork 8
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
gps rr: don't push to remote if the remote branch contains commits without a ps-id #293
Comments
@Talor-A thx for starting this conversation. We compute state information in other places about the associated branches (local & remote). You can see this for example in the So we should be able to use that same stuff to add some sort of safety checking for this. I can't think of an easy way to do this with hooks as all the state computation stuff exists in the core code base. In the mean time though you should be able to see this state via the
|
When we implement this we probably shouldn't just use the general state computation that computes state for all branches as that is a bunch of un-necessary work. We should add support for computing state for a particular branch, it's associated tracking branch, as well as the stack probably. |
hey all! loving using
gps
for my daily git workflows. I'm noticing a small rough edge with the tool it would be good to have some safeguards for. the docs note that if yougps rr
a branch that might've had external changes committed to it, we'll force push overwrite those changes. I wonder if it would be possible to first check for aps-id
in each commit in the remote branch, and abort the change if so?maybe this is possible to implement today, with hooks?
The text was updated successfully, but these errors were encountered: