You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Renaming the current branch doesn't cause a message to be written to the HEAD reflog #4292
Just a heads up, I think you want git_branch_move (eg. git branch -m develop) instead of git_reference_rename (eg. git update-ref development refs/heads/develop). I haven't checked what the reflog show in that case though, so YMMV.
@tiennou Thanks! IIRC, git_branch_move calls git_reference_rename under the hood; while I'm not 100% sure of that, my testing did show git_branch_move to have the same problem with the reflog.
Just checked, and there's still only the reflog line added by git_repository_set_head in the HEAD reflog. Hopefully, I'll have a preliminary PR soon-ish.
(Sorry for the spam, I rebased the test and pushed the wrong one 😟)
Activity
tests: test case for libgit2#4292
tests: test case for libgit2#4292
tests: test case for libgit2#4292
tiennou commentedon Jul 17, 2017
Just a heads up, I think you want
git_branch_move(eg.git branch -m develop) instead ofgit_reference_rename(eg.git update-ref development refs/heads/develop). I haven't checked what the reflog show in that case though, so YMMV.jgrosso commentedon Jul 17, 2017
@tiennou Thanks! IIRC,
git_branch_movecallsgit_reference_renameunder the hood; while I'm not 100% sure of that, my testing did showgit_branch_moveto have the same problem with the reflog.tests: test case for libgit2#4292
tests: test case for libgit2#4292
tiennou commentedon Jul 17, 2017
Just checked, and there's still only the reflog line added by
git_repository_set_headin theHEADreflog. Hopefully, I'll have a preliminary PR soon-ish.(Sorry for the spam, I rebased the test and pushed the wrong one 😟)
tests: test case for libgit2#4292