Skip to content

Commit db64145

Browse files
authored
Merge pull request #2954 from zeenix/doc-rfc-num
Document when and how a number is assigned to RFC file
2 parents 80ef84e + 6033bd9 commit db64145

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,8 @@ merged into the RFC repository as a markdown file. At that point the RFC is
105105

106106
- Fork the RFC repo [RFC repository]
107107
- Copy `0000-template.md` to `text/0000-my-feature.md` (where "my-feature" is
108-
descriptive. don't assign an RFC number yet).
108+
descriptive). Don't assign an RFC number yet; This is going to be the PR
109+
number and we'll rename the file accordingly if the RFC is accepted.
109110
- Fill in the RFC. Put care into the details: RFCs that do not present
110111
convincing motivation, demonstrate lack of understanding of the design's
111112
impact, or are disingenuous about the drawbacks or alternatives tend to

0 commit comments

Comments
 (0)