June 30, 2011 at 15:54Cheat sheet for beginners
- Tutorial
If at one point you were struck by the desire to plant a reasonable, kind, eternal, and transfer everyone from SVN to GIT, three problems immediately arise:
Since we use a very effective scheme for working with code through git in one of the projects, I decided to implement it everywhere I reached my hands, for which I designed a small cheat sheet containing short answers to “Why,” a description of the working scheme and list of commands and body movements for the developer with the new system.
Basic principles of working with code:
Since for some reason some developers work under Windows, I had to describe including setting-setting-recipes when working under Windows.
I throw the received instruction at all new and old developers, whom I give access to repositories with working code.
I warn you right away, the instruction answers the question “why” to a developer unfamiliar with DVCS, and not to the authorities.
It is also assumed that the master branch is never touched with --force, it is desirable that this was not possible at all (slaughtered at the gitolite level).
The instruction is for beginning developers, not Tips & Tricks, for these reasons I omitted the moments of “getting out of a self-created ass”. I don’t remember all the cases, it’s much easier to resolve on the spot in fact if something out of the ordinary.
Actually instruction:Work with Git.pdf (135Kb) .
For those who want to adapt it to their situation, source: Working with Git.odt (90Kb) .
ps: Forgot to say about the license: Public Domain. Do what you want, only do not throw in the thorn bush.
I would be grateful for any useful comments, pointing to the camera, and other feedback.
- Explain why developers and management need it
- Introduce a new code scheme
- Teach unsuspecting developers new techniques
Since we use a very effective scheme for working with code through git in one of the projects, I decided to implement it everywhere I reached my hands, for which I designed a small cheat sheet containing short answers to “Why,” a description of the working scheme and list of commands and body movements for the developer with the new system.
Basic principles of working with code:
- Each task is solved in its own branch.
- Commit right away, as something got meaningful.
- In master, it’s not the developer, but the second person who proofreads and tests the changes.
- All commits must be meaningfully signed.
- The repository should be kept dry and silky.
Since for some reason some developers work under Windows, I had to describe including setting-setting-recipes when working under Windows.
I throw the received instruction at all new and old developers, whom I give access to repositories with working code.
I warn you right away, the instruction answers the question “why” to a developer unfamiliar with DVCS, and not to the authorities.
It is also assumed that the master branch is never touched with --force, it is desirable that this was not possible at all (slaughtered at the gitolite level).
The instruction is for beginning developers, not Tips & Tricks, for these reasons I omitted the moments of “getting out of a self-created ass”. I don’t remember all the cases, it’s much easier to resolve on the spot in fact if something out of the ordinary.
Actually instruction:Work with Git.pdf (135Kb) .
For those who want to adapt it to their situation, source: Working with Git.odt (90Kb) .
ps: Forgot to say about the license: Public Domain. Do what you want, only do not throw in the thorn bush.
I would be grateful for any useful comments, pointing to the camera, and other feedback.