-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
[FIX] Store full commit hash in version sync file instead of short #205
Comments
Hello apologies for the delayed response, please go ahead. and everywhere u see EDIT: you can create a var called |
@isak102 hello can you confirm this PR works for you? |
Thanks! Yes it is working |
Great I'll have to tweak it a bit before i can finally ship it since bob currently saves the build with the shortened hash which needs to be tweaked (ill probably write the full hash in a file. |
Yeah my bad, I didnt test actually opening Neovim, I just looked if it was saving the full hash in the file. When I try to open neovim I get this error
|
ye lol |
@isak102 It should work now, the steps to test is:
|
I regularly run into this problem when trying to use
bob sync
Is there any specific reason why the short hash is stored in the version sync file and not the full hash? If not, I am willing to open a PR to fix this
The text was updated successfully, but these errors were encountered: