mirror of
https://github.com/urbit/shrub.git
synced 2024-08-17 08:00:39 +03:00
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.
This commit is contained in:
parent
2a517b59f3
commit
599759cc38
@ -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
|
feature request; instead, try to be specific about what you're requesting, and
|
||||||
what your desired feature would accomplish.
|
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/<N>/<...>`, where `<N>` 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/<N>` a well-formed branch name. These feature branches should be based
|
|
||||||
off of `develop`.
|
|
||||||
|
|
||||||
### Commits
|
### Commits
|
||||||
|
|
||||||
Commits should generally be relevant, atomic, and have descriptions formatted in
|
Commits should generally be relevant, atomic, and have descriptions formatted in
|
||||||
|
Loading…
Reference in New Issue
Block a user