git
Will Faught
Home
Will Faught
Sean Patterson: Commit each fix or task as a separate change Only commit when a block of work is complete Commit each layout change separately Joint commit for layout file, code behind file, and additional resources Invaluable advice for keeping a sane commit history.
1 minute
How To Write A Git Commit Message
Chris Beams: A project’s long-term success rests (among other things) on its maintainability, and a maintainer has few tools more powerful than his project’s log. It’s worth taking the time to learn how to care for one properly. What may be a hassle at first soon becomes habit, and eventually a source of pride and productivity for all involved. In this post, I am addressing just the most basic element of keeping a healthy commit history: how to write an individual commit message.
1 minute
“Master,” said the novice, “what is the nature of long and short options for commands? I thought they were equivalent, but when that developer used -h you said something different than when I said –help.” “Perspective is everything,” answered the Master. The novice was puzzled. She decided to experiment and said “git -h branch”. Master Git turned and threw himself off the railing, falling to his death on the rocks below.
1 minute
An excellent explanation of how Git works internally. Simple and beautiful.
1 minute
It took me ten minutes and a Google search to figure out how to post a comment for a change in Gerrit.
1 minute
If you’re a programmer and you’re not using a distributed version control system, you’re doing yourself a disservice. Learn why Git is better than your version control system and then learn how it works.
coding git technology version control
1 minute