From a4f4c70c6006f99c650702dc2f21a88ddf62e0db Mon Sep 17 00:00:00 2001 From: Julien Pivotto Date: Mon, 25 Sep 2017 17:29:19 +0200 Subject: [PATCH] mons-months: fix typo in maintainer-etiquette --- docs/maintainer-etiquette.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/maintainer-etiquette.md b/docs/maintainer-etiquette.md index eb3f90064..30fd69a72 100644 --- a/docs/maintainer-etiquette.md +++ b/docs/maintainer-etiquette.md @@ -26,7 +26,7 @@ These apply to all contributors, but maintainers should lead by examples! :wink: - if the PR submitter has push privileges (recognizable via `Collaborator`, `Member` or `Owner` badge) - we expect **the submitter** to merge their own PR after receiving a positive review from either HC employee or another maintainer. _Exceptions apply - see below._ - we prefer to use the Github's interface or API to do this, just click the green button - squash? - - squash when you think the commit history is irrelevant (will not be helpful for any readers in T+6mons) + - squash when you think the commit history is irrelevant (will not be helpful for any readers in T+6months) - Add the new PR to the **Changelog** if it may affect the user (almost any PR except test changes and docs updates) - we prefer to use the Github's web interface to modify the Changelog and use `[GH-12345]` to format the PR number. These will be turned into links as part of the release process. Breaking changes should be always documented separately.