octo
/
Zebra
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make the RFC TOC into a separate step (#2126) 

We might remember it better that way.
This commit is contained in:
teor 2021-05-10 23:17:42 +10:00 committed by GitHub
parent 29893f2b9b
commit 8b72e8627b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
CONTRIBUTING.md
View File

@ -74,9 +74,10 @@ with the PR number.
8. When the RFC is merged, take the next available RFC number (not conflicting 8. When the RFC is merged, take the next available RFC number (not conflicting
with any existing RFCs or design PRs) and name the RFC file accordingly, e.g., with any existing RFCs or design PRs) and name the RFC file accordingly, e.g.,
`0027-my-feature.md` for number 27. Make sure that `book/src/SUMMARY.md` links `0027-my-feature.md` for number 27.
to the numbered RFC.
7. After the RFC is accepted, create an issue for the implementation of the 9. Make sure that `book/src/SUMMARY.md` links to the new number for the RFC.
10. After the RFC is accepted, create an issue for the implementation of the
design, and update the RFC header and PR description with the implementation design, and update the RFC header and PR description with the implementation
issue number. issue number.