-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Known issues #1
Labels
bug
Something isn't working
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
git next
doesn't complain if you try to go ahead more commits than exist. (Instead, it just goes to the last possible commit.) There should probably be a specific flag to go the maximum number of commits forward instead.post-rewrite
hook. There is no way to recover the knowledge of which commits were dropped after the fact.git move
enhancements #34.git branchless init
should autodetect the main branch name. For example, if there is no branch namedmaster
in the current repository, but there is a branch namedmain
, then we should automatically configure branchless to usemain
in that case.git reset
with--soft
/--hard
leaves the old commit in the smartlog. It would probably be best to remedy this by adding additional primitives which solve the use-cases forgit reset
, such asgit split
and/orgit uncommit
commands.git rebase
s leave any applied commits in the smartlog.git undo
returns you to a historical commit, but doesn't check out the appropriate branch attached to that commit, if any. Fixing this requires a database schema change.git restack
loops forever for some merge commits.restack
appears to enter infinite loop when it encounters a merge conflict #33.git undo
view to corner #63.git undo
view to corner #63.eyre::bail!
calls can happen during normal operation. These should be fixed to use normal error messaging.The text was updated successfully, but these errors were encountered: