Git for Programmers by Jesse Liberty

Author:Jesse Liberty
Language: eng
Format: epub
Publisher: Packt
Published: 2021-06-24T18:11:21+00:00

Rebase early and rebase often

It is very good practice to rebase frequently, so as to surface any conflicts that might arise. Each time you rebase, you end up with a stack of commits that has all that came before and then your new commits at the tip. If a conflict arises between what you just added and what was there, you will see it immediately and can fix it on the spot.

Rebase locally only

You rebase only on your local machine, and never on the shared repository in the cloud (for example, GitHub). This is because rebasing "rewrites history" – remember that it makes copies of Feature1 – and if another programmer is working on that branch, they will not be happy with you if you rebase. This is the kind of "not happy" that can lead to felony charges.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.