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
Being able to see the entire Git repository graph, not just the reachable commits, is very helpful for debugging git issues. For example, if you run: git reset HEAD~1 --soft, the branch pointer will move to its parent commit. But you may still want to see the child commit.
By default, we should only show the reachable commits. But let's have a toggle button that will show all commits in the git repo graph. The non-reachable commits should be slightly greyed out or something to indicate they're in an unreachable state.
The text was updated successfully, but these errors were encountered:
@haacked the binary from your blog post http://haacked.com/archive/2012/03/15/visualize-git-with-seegit.aspx has this feature. That is it shows dangling (unreachable) commits though current version (built from master) doesn't.
Could you give me a pointer as to what could've changed for it to get intentionally or unintentionally broken?
@mdonatas Yeas, that's the current behavior. Because we don't refresh our UI graph when commits go away. I'd like to have it show all commits, but that'd be a little tricky. We'd need to parse the reflog to find commits we might not know about. If it's not reachable, it's generally not easy to get a reference to it. :)
Being able to see the entire Git repository graph, not just the reachable commits, is very helpful for debugging git issues. For example, if you run:
git reset HEAD~1 --soft
, the branch pointer will move to its parent commit. But you may still want to see the child commit.By default, we should only show the reachable commits. But let's have a toggle button that will show all commits in the git repo graph. The non-reachable commits should be slightly greyed out or something to indicate they're in an unreachable state.
The text was updated successfully, but these errors were encountered: