Forked from
R3 / school / courses
523 commits behind the upstream repository.
-
Laurent Heirendt authoredLaurent Heirendt authored
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
best_practices.md 742 B
Best practices
-
pull
beforepush
-
Work on your own branch (in your own fork), and not on
master
and not ondevelop
-
Do not push to
master
ordevelop
, but submit a PR/MR -
Get your code reviewed by your peers (submit a PR/MR!)
-
Submit a PR/MR often!
-
clone
a repository, do not download the.zip
file. -
Do not combine
git
commands$ git commit -am "myMessage" # do not do this
-
Stage only 1 file at once using
$ git add myFile.txt
-
Commit only a few files at once (after multiple separate
git add
commands) -
Push
often - avoid conflicts
Remember: A push
a day keeps conflicts away!