Updating the currently checked out branch this may cause confusion
There are few things more frustrating than trying to make other peoples’ code work; broken references, missing dependencies, extraneous and useless files – it’s all part of the joy of sharing the project love around.
This is often tricky enough for people on the same team but throw in distance, culture and varying levels of expertise and things get ugly pretty quickly.
Best Practices vary from environment to environment, and there is no One True Answer, but still, this represents a consensus from #git and in some cases helps you frame the discussion for the generation of your very own best practices.
Git only takes full responsibility for your data when you commit.
For a less formal usage, like say this document I let people see what really happened.
) your work will not be lost for at least two weeks unless you really work at it (run commands that manually purge it).
If you fail to commit and then do something poorly thought out, you can run into trouble.
Additionally, having periodic checkpoints means that you can understand how you broke something.
Branches are just pointers that point at specific commits.So if you're going to write or customize Koha code, take a few minutes to familiarize yourself with the primary tool us Koha developers use for version control.This should be considered a working document, as we all get used to using Git, and we get more developers on board, our workflow is likely to change.$ git clone git://git.koha-community.org/kohaclone remote: Generating pack... remote: Total 16310, written 16310 (delta 10657), reused 12014 (delta 7834) 100% (16310/16310) done Resolving 10657 deltas. 100% (3429/3429) done To clone the repository using the Git protocol (git:), you need to be able to connect to port 9418 on git.If for some reason you have a restrictive firewall that cannot be changed, and using SSH port forwarding is not an option, it is possible to clone the repository using HTTP: Other Git operations such as "git fetch" and "git rebase" will work normally after you clone using HTTP.