best_practices.md 742 Bytes
Newer Older
1
2
3
4
5
6
## Best practices

* `pull` before `push`

* Work on your <font color="red">own</font> branch (in your own fork), and **not** on `master` and **not** on `develop`

Laurent Heirendt's avatar
Laurent Heirendt committed
7
* Do **not push** to `master` or `develop`, but **submit a PR/MR**
8

Laurent Heirendt's avatar
Laurent Heirendt committed
9
* Get your code **reviewed** by your peers (submit a PR/MR!)
10

Laurent Heirendt's avatar
Laurent Heirendt committed
11
* Submit a PR/MR **often**!
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

* `clone` a repository, do not download the `.zip` file.


* Do **not** combine `git` commands
   ```bash
   $ git commit -am "myMessage" # do not do this
   ```

* Stage only 1 file at once using

   ```bash
   $ git add myFile.txt
   ```

* Commit **only a few files** at once (after multiple separate `git add` commands)

* `Push` often - avoid conflicts

<br><br>
Remember: **A `push` a day keeps conflicts away!**