diff options
| author | syuilo <Syuilotan@yahoo.co.jp> | 2022-02-06 21:50:31 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-06 21:50:31 +0900 |
| commit | ec23e6270ba3a62f0ee71cb45ae59c75f5c991d7 (patch) | |
| tree | 7995e3c4a6322c46b9b772c435a1a918944ea756 /CONTRIBUTING.md | |
| parent | Update CONTRIBUTING.md (diff) | |
| download | misskey-ec23e6270ba3a62f0ee71cb45ae59c75f5c991d7.tar.gz misskey-ec23e6270ba3a62f0ee71cb45ae59c75f5c991d7.tar.bz2 misskey-ec23e6270ba3a62f0ee71cb45ae59c75f5c991d7.zip | |
Update CONTRIBUTING.md
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bc36d5e421..ffd84fc851 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -16,7 +16,7 @@ Before creating an issue, please check the following: ## Before implementation When you want to add a feature or fix a bug, **first have the design and policy reviewed in an Issue** (if it is not there, please make one). Without this step, there is a high possibility that the PR will not be merged even if it is implemented. -At this point, you also need to clarify the goals of the PR you are creating, and make sure that the other members of the team are aware of them. +At this point, you also need to clarify the goals of the PR you will create, and make sure that the other members of the team are aware of them. PRs that do not have a clear set of do's and don'ts tend to be bloated and difficult to review. Also, when you start implementation, assign yourself to the Issue (if you cannot do it yourself, ask another member to assign you). By expressing your intention to work the Issue, you can prevent conflicts in the work. |