kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Fix typo in CONTRIBUTING.md

Browse Source 
Signed-off-by: Tom Chauveau <tom.chauveau@epitech.eu>
This commit is contained in:
Tom Chauveau 2021-07-29 18:29:45 +02:00
parent 82d95a5c64
commit 6976e32290
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
CONTRIBUTING.md
View File

@ -29,7 +29,7 @@ git remote add fork git@github.com:MYFORK/dagger.git
# create a branch # create a branch
git checkout -b mybranch git checkout -b mybranch
# make chances to your branch, use `git commit -s`, ... # make changes to your branch, use `git commit -s`, ...
# ... # ...
# push the branch to your own fork # push the branch to your own fork
@ -71,9 +71,8 @@ Guidelines:
- Group Commits: Each commit should represent a meaningful change (e.g. implement - Group Commits: Each commit should represent a meaningful change (e.g. implement
feature X, fix bug Y, ...). feature X, fix bug Y, ...).
- For instance, a PR should not look like _1) Add Feature X 2) Fix Typo 3) Changes to features X 5) Bugfix for feature X 6) Fix Linter 7) ..._ - For instance, a PR should not look like _1) Add Feature X 2) Fix Typo 3) Changes to features X 5) Bugfix for feature X 6) Fix Linter 7) ..._<br>
- Instead, these commits should be squashed together into a single "Add Feature" Instead, these commits should be squashed together into a single "Add Feature" commit.
commit.
- Each commit should work on its own: it must compile, pass the linter and so on. - Each commit should work on its own: it must compile, pass the linter and so on.
- This makes life much easier when using `git log`, `git blame`, `git bisect`, etc. - This makes life much easier when using `git log`, `git blame`, `git bisect`, etc.
- For instance, when doing a `git blame` on a file to figure out why a change - For instance, when doing a `git blame` on a file to figure out why a change