1 files changed, 2 insertions, 1 deletions
diff --git a/docs/dev/style.md b/docs/dev/style.md
index 2454087e8..44f0956c2 100644
--- a/docs/dev/style.md
+++ b/docs/dev/style.md
@@ -239,8 +239,9 @@ If the line is too long, you want to split the sentence in two :-)
 # Commit Style
 We don't have specific rules around git history hygiene.
-Maintaining clean git history is encouraged, but not enforced.
+Maintaining clean git history is strongly encouraged, but not enforced.
 Use rebase workflow, it's OK to rewrite history during PR review process.
+After you are happy with the state of the code, please use [interactive rebase](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) to squash fixup commits.
 Avoid @mentioning people in commit messages and pull request descriptions(they are added to commit message by bors).
 Such messages create a lot of duplicate notification traffic during rebases.

diff --git a/docs/dev/style.md b/docs/dev/style.md index 2454087e8..44f0956c2 100644 --- a/docs/dev/style.md +++ b/docs/dev/style.md
@@ -239,8 +239,9 @@ If the line is too long, you want to split the sentence in two :-)
239	# Commit Style	239	# Commit Style
240		240
241	We don't have specific rules around git history hygiene.	241	We don't have specific rules around git history hygiene.
242	Maintaining clean git history is encouraged, but not enforced.	242	Maintaining clean git history is strongly encouraged, but not enforced.
243	Use rebase workflow, it's OK to rewrite history during PR review process.	243	Use rebase workflow, it's OK to rewrite history during PR review process.
		244	After you are happy with the state of the code, please use [interactive rebase](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) to squash fixup commits.
244		245
245	Avoid @mentioning people in commit messages and pull request descriptions(they are added to commit message by bors).	246	Avoid @mentioning people in commit messages and pull request descriptions(they are added to commit message by bors).
246	Such messages create a lot of duplicate notification traffic during rebases.	247	Such messages create a lot of duplicate notification traffic during rebases.