github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Better wording for clean up. 

Encouraging squashing by default leads to important history being lost. People new to different git flows may be doing themselves and the project a disservice without knowing.
pull/6/head
Adam Dymitruk 2015-03-23 23:51:46 -07:00
parent d0b468f4b0
commit e94b561623
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/devel/faster_reviews.md
View File

@ -120,8 +120,8 @@ your whole PR is pretty trivial, you should instead put your fixups into a new
commit and re-push. Your reviewer can then look at that commit on its own - so
much faster to review than starting over.
We might still ask you to squash commits at the very end, for the sake of a clean
history.
We might still ask you to clean up your commits at the very end, for the sake
of a more readable history.
## 8. KISS, YAGNI, MVP, etc