Really, a reflog entry appears for each state at begin and end of each rebase, so they at least can be recovered.
has some safeguards for timeline-incompatible changes (i.e. file existed at the time but had entirely different contents)
That's why, an opposite, a file could be easily edited with the edited commit but not later.
Similarly, I would avoid the restore command, instead using checkout and reset where appropriate.
restore is a new command which just unifies multiple use cases for former checkout, branch and reset under a convenient common name. It hasn't added new functionality. To use restore or older variants is still just a matter of taste.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Really, a reflog entry appears for each state at begin and end of each rebase, so they at least can be recovered.
That's why, an opposite, a file could be easily edited with the edited commit but not later.
restoreis a new command which just unifies multiple use cases for formercheckout,branchandresetunder a convenient common name. It hasn't added new functionality. To userestoreor older variants is still just a matter of taste.