From 599759cc383653a145727b182dea7bd558199e18 Mon Sep 17 00:00:00 2001 From: Ted Blackman Date: Wed, 24 May 2023 11:40:45 -0400 Subject: [PATCH] Update CONTRIBUTING.md We no longer recommend creating an issue to correspond to a PR or using that issue's name in the branch name for the PR. That was useful when ZenHub was used for tracking PRs, but it's not anymore. --- CONTRIBUTING.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 59db35a6b..69cdb7006 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -31,15 +31,6 @@ them. "It would be cool if.." probably does not, in itself, constitute a good feature request; instead, try to be specific about what you're requesting, and what your desired feature would accomplish. -### Feature Branch Names - -Every branch that you intend to put up for review must adhere to the form -`i//<...>`, where `` is the number of the issue that the branch -corresponds to and `<...>` is an optional short description of the branch to aid -in readability. If `<...>` is omitted, the `/` should be omitted as well, which -makes `i/` a well-formed branch name. These feature branches should be based -off of `develop`. - ### Commits Commits should generally be relevant, atomic, and have descriptions formatted in