Closed mlcui-corp closed 1 year ago
Oops, thanks for reporting. Can you see if #634 resolves the issue?
Do you use git smartlog --hidden
as part of your normal workflow, or is it just to expose the issue?
Yep, I can confirm #634 fixes the issue.
Do you use
git smartlog --hidden
as part of your normal workflow, or is it just to expose the issue?
No, I don't use it as part of my normal workflow. I stumbled across this issue when I was demo-ing git-branchless
to some coworkers who were familiar with Mercurial's changeset evolution workflow. git smartlog --hidden
is a great way of demoing bitemporality, especially after a git sync
, but it wasn't working (hence this bug report).
edit: To be exact, I stumbled across this before my demo (no buggy behaviour was demoed 😛). I instead used git commit --amend
to create an abandoned commit, then git restack
, to show bitemporality.
To be exact, I stumbled across this before my demo
That's a relief 😂
Description of the bug
After doing a few
git sync
s in a repo,git smartlog --hidden
should show commits that were rewritten. However, at HEAD,git smartlog --hidden
shows the same output asgit smartlog
.The culprit commit is c90b52f5e1c379959952b59d2f2d0cc976ed4938. Specifically, creating a revert of it at fbe7766 fixes the issue (as I didn't want cargo to rebuild a lot of packages by going back that far).
Expected behavior
git smartlog --hidden
shows hidden commits.Actual behavior
git smartlog --hidden
does not show hidden commits.Version of
rustc
No response
Automated bug report
No response
Version of
git-branchless
No response
Version of
git
No response