how to add commit and push in git on mac

Continuous integration services (such as Travis) require you to push code to test it. Or if you work like this, maybe you will! There will come a time months or years from now when you will look at your code and you won't remember why you wrote it that way. If you push broken code, pushing is inflicting your work on others. If you always have to question whether the code in the shared repository works, it slows work down immensely. Then they know any failure is the fault of the merge. Other people on the project (including those in the future) should have a reasonable expectation that code they pull works. It is very important to avoid pushing broken code, even in a branch. Unlike Subversion, Git deliberately separates the concept of commit and push. If your code isn't ready to be shared with others, don't push it. Habitually pushing at the end of the day is even worse. It relies on the idea that each commit is working code. It can automatically find the commit which caused a bug. Git has an even more powerful debugging tool called bisect. Then you lose this very powerful debugging technique. If you just commit at the end of the day, you're likely to commit broken code. What broke the code? Something in git diff. If you only commit when all tests pass, then debugging is much easier. If you log everything you've done for the day, the commits will be too big, contain multiple changes, and it will be difficult to figure out what code goes with what change.Ĭommits are also very useful as checkpoints for the last time the code worked. If the commits are just whatever you did today, that's help to no one.

This splits up the changes into easy to review chunks, and it makes it easy to describe what you've done. Fixed a bug, added a feature, changed a name, and so on. At it's most basic level it must answer the question 'why is this code written this way?' Commits should be done when you've finished a single logical change. It has to be useful to someone else trying to understand your code in the future (who might be you in six months). A simple trick is to put your project files in a Dropbox folder or the like.Ĭommits in git are about creating a record of why changes were made. There's a number of free, automatic, online backup services to choose from.

How to add commit and push in git on mac