-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add support for --update-ref #872
Comments
Thanks for the issue! update-ref support was added this past November, however, looking at that version number, it should be working for you. Probably a bug in the parsing, let me take a look! |
@glensc , can you give version 2.3.0 a try? It was released yesterday, and update-ref seems to be working in all my tests. If it's not working, mind sharing the update-ref line(s) that is failing for you? You can anonymize it. |
@MitMaro I think the problem is not about
the editor is not even launched, aborts with error:
from my
|
Update: seems 2.3.0 was released just 2 days ago: so, that's why it's not yet in brew. and can't run the file directly from downloads, killed as not from a verified developer
so have to wait for brew update to test :) |
Update2: brew update pr is here, but currently build failing: |
This feature was implemented in 2.3.0, and I have been using it myself with |
Thanks @neersighted ! Good to hear that it's been working for you over the past several months. I will keep the issue open until @glensc can confirm that it works on their system (once 2.3.0 hits homebrew), just in case there is some odd edge case. |
2.3.0 hit homebrew! |
I can confirm 2.3.0 no longer gives the parse error! |
https://adamj.eu/tech/2022/10/15/how-to-rebase-stacked-git-branches/
suggests to set the flag globally:
yet this breaks this tool:
please add support for the flag, and maybe (if needed)
update-ref
command typeThe text was updated successfully, but these errors were encountered: