4 ms·
I don't understand. You can always restore any previous state using git, I used to do it from the command line. If I use github desktop I can roll back a commi
by whiddershins 5y ago
I don't understand. You can always restore any previous state using git, I used to do it from the command line.
If I use github desktop I can roll back a commit whenever I like with a simple menu command.
What am I missing here. I feel like I don't understand what the tool is doing.
- nerdponx 5y agohttps://github.com/arxanas/git-branchless/wiki/Architecture#comparison-with-the-reflog https://github.com/arxanas/git-branchless/wiki/Architecture#...
- whalesalad 5y agoIf you understand the fundamentals of a version control system I find git relatively intuitive to use. Sometimes I don’t know the exact cli syntax for a complicated procedure but that’s easy enough to figure out if you know the concepts. Most people fail to learn the concepts and then try to brute force everything.
- cerved 5y agoMost people do not even seem the slightest inclined to bother. It's a sad attitude IMHO
- jonahx 5y agoThe README for the parent repo (https://github.com/arxanas/git-branchless https://github.com/arxanas/git-branchless) answers these questions in detail. Short answer, recreating this tool's features in vanilla git requires using the reflog, which isn't user-friendly: > Why not git reflog? > git reflog is a tool to view the previous position of a single reference (like HEAD), which can be used to undo operations. But since it only tracks the position of a single reference, complicated operations like rebases can be tedious to reverse-engineer. git undo operates at a higher level of abstraction: the entire state of your repository.