3 ms·
Learning git is not easy. There is one thing that will almost guarantee no work is ever lost: commit. if something is commit, even if it’s not pushed it can be
by joe8756438 4y ago
Learning git is not easy.
There is one thing that will almost guarantee no work is ever lost: commit. if something is commit, even if it’s not pushed it can be retrieved.
One other thing that has nothing to do with how it works, but makes all the difference in usability: write commit messages describing _why_.
To learn git is to use git, reading about it has not helped me.
- shikoba 4y ago> write commit messages describing _why_. Could you provide a concrete example? I don't understand your point.
- joe8756438 4y agoAs in: "changed this property in the config _because_ it will extinguish all evil from planet earth" vs. "changed this property in the config". I can see _what_ somebody did well enough from the code diff itself -- reading an uninterrupted stream of messages explaining _why_ in a git log is a wonderful experience.
- shikoba 4y agoThank you, I think I get your idea.