61–70 of 146 posts
I liked the way I learned git. I started with sourcetree, a third party git gui. Super simple to use and understand. Then I moved to git gui, this step could be skipped. Then I got tired of pulling up my UIs and learned the terminal commands. Highly suggest this for anyone new, but just my (n=1) experience.
Btw I moved from Sourcetree to Fork. It’s very similar but way more performant and smooth UI (unless ST has improved in last few years)
Earlier quoted context omitted.
Life is simple until we play with time, once you start altering the past everything falls apart
It's not possible to alter commits with git. They are immutable. You can only make new commits that are based on existing ones in some way. The distinction is important, because the original commit (such as a commit pre-rebase) still exists after it's been "changed".
The original commit will only exist for as long as git deigns not to garbage collect it.
Earlier quoted context omitted.
Life is simple until we play with time, once you start altering the past everything falls apart
It's not possible to alter commits with git. They are immutable. You can only make new commits that are based on existing ones in some way. The distinction is important, because the original commit (such as a commit pre-rebase) still exists after it's been "changed".
Earlier quoted context omitted.
All I know of git is clone, pull, commit, and push. That’s all I’ve ever needed. Git can be that simple. Of course it supports more complex uses, which you can learn if you need them.
Life is simple until we play with time, once you start altering the past everything falls apart
Later on, you can apply it if necessary with "git apply works.patch".
git log -LstartLine,endLine:fileName
Answers the questions of "who did this, when, and why?" / "How long has it been like that?", etc.
Is there a historical reason why git is needlessly complex? Seeing this cheat sheet really brings it to life.
In newer versions of git the cost of adding new subcommands is reduced and they've started adding more specific commands like git switch.
I liked the way I learned git. I started with sourcetree, a third party git gui. Super simple to use and understand. Then I moved to git gui, this step could be skipped. Then I got tired of pulling up my UIs and learned the terminal commands. Highly suggest this for anyone new, but just my (n=1) experience.
All I know of git is clone, pull, commit, and push. That’s all I’ve ever needed. Git can be that simple. Of course it supports more complex uses, which you can learn if you need them.
I have a funny little habit that probably stems from a certain degree of paranoia when working on a decent-sized change. I like to keep a local patch of it, as follows: "git diff > works.patch" Later on, you can apply it if necessary with "git apply works.patch".