diff options
| author | Matthias Beyer <matthias.beyer@ifm.com> | 2022-08-31 11:07:40 +0200 |
|---|---|---|
| committer | Matthias Beyer <matthias.beyer@ifm.com> | 2022-09-01 17:46:58 +0200 |
| commit | 430526615746a9a675f36908e17d131cb481d6c5 (patch) | |
| tree | e916c447f8f143498a8a42d70f41669e206b454c | |
| parent | b7616697448bb2cc31df197dd0d9126de583dd97 (diff) | |
Remove section on auto-close functionality
Rationale being that we do not yet have a "testers" team or anything
like that.
Once we have these defined, we might re-add a paragraph like this.
Signed-off-by: Matthias Beyer <matthias.beyer@ifm.com>
| -rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4371d837..74fd6e92 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,12 +33,6 @@ When possible, fill out as much detail in the pull request template as is reasonable. Most important is to reference the GitHub issue that you are addressing with the PR. -**NOTE:** GitHub has [a feature](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) -that will automatically close issues referenced with a keyword (such as "Fixes") -by a PR or commit once the PR/commit is merged. Don't use these keywords. We -don't want issues to be automatically closed. We want our testers to -independently verify and close them. - ## Writing good commit messages Git commit messages should explain the how and why of your change and be |