How do you avoid that people forget to run 'git push'? -

While evaluating the advantages and disadvantages of taking our Subversion-based repository to the cit, an interesting question was raised.

Even if we like all the guitars very much, it could be that some developers (or developers' teams) forget about pushing a feature / bugfix on the repository that makes the package .

I am sure that this concern has already been raised in other software development teams, I wonder how you faced this problem.

I agree that ideally you can fix it by trying to give a lot of reminders. Some different ideas:

• Some things that strengthen the distributed version control idea will help people think more naturally about this. For example, I support a workflow that involves the use of local theme branches and as long as they do not really want to, I am amending / reducing the reservation. If you teach how to do this, then it becomes clear that this is the work done in your own field. As the developers are more aware that their repo is different from the central, remembering the push will be very easy.

• If you assign a reminder to your master branch (or any other branch that tracks a branch at the root), git-status "Your branch is ahead of 'Basic / Master' from 1 branch." You will also see when you examine the master.

• If you want, if you really wanted, write a post-cut hook that tells the user how far they are apart from the original, depending on your workflow. There are several ways to reach - maybe repeat the status message, perhaps the oldest of the current branch is committed that is not in the original, so that you can tell them how long it has been ... Note that hooks with the repository Not too trivial: .git / hooks Is not tracked, so you have to symink the hook in the reporter in the directory or inside it, this setup can be automated by the script, however, it is not very bad!