* https://chriskottom.com/blog/2014/02/a-few-modest-best-practices-forgit/ * htt
ID: 3863138 • Letter: #
Question
* https://chriskottom.com/blog/2014/02/a-few-modest-best-practices-forgit/
* https://sethrobertson.github.io/GitBestPractices/
* https://www.lullabot.com/articles/git-best-practices-workflow-guidelines
* https://www.git-tower.com/learn/git/ebook/en/command-line/
* appendix/best-practices
* https://blog.hartleybrody.com/git-small-teams/
Explanation / Answer
I am summerizing Github best prctices in following points.
1. create a branch from master, check it out, do your work
2. test and commit your changes
3. optionally push your branch up to the remote repository (origin) OR
4. optionally rebase your branch to master (if your changes are unpublished)
5. checkout master, make sure it's up-to-date with upstream changes
6. merge your branch into master
test again (and again)
7. push your local copy of master up to the remote repository master (origin/master)
8. delete your branch (and remotely, too, if you published it)
9. NEVER force a push. If you find yourself in a situation where your changes can't be pushed upstream, something is wrong. Contact another Fedora developer for help tracking down the problem.
10. NEVER rebase a branch that you pushed, or that you pulled from another person. Rebasing published branches can lead to duplicate commits in the shared repository.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.