From 26be211e5d2dd4ca2b92747e19004fa1912685f9 Mon Sep 17 00:00:00 2001 From: Arseny Kapoulkine Date: Tue, 4 May 2021 16:23:45 -0700 Subject: [PATCH] Update README.md Emphasize the rfc label even more. --- rfcs/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/rfcs/README.md b/rfcs/README.md index a1f5fa8..02f83f5 100644 --- a/rfcs/README.md +++ b/rfcs/README.md @@ -25,7 +25,9 @@ Since reversing these decisions is incredibly costly and can be impossible due t Process === -To open an RFC, a Pull Request must be opened which creates a new Markdown file in `rfcs/` folder. The RFCs should follow the template `rfcs/TEMPLATE.md`, and should have a file name that is a short human readable description of the feature (using lowercase alphanumeric characters and dashes only). Try using the general area of the RFC as a prefix, e.g. `syntax-generic-functions.md` or `function-debug-info.md`. **The PR needs to use `rfc` label.** +To open an RFC, a Pull Request must be opened which creates a new Markdown file in `rfcs/` folder. The RFCs should follow the template `rfcs/TEMPLATE.md`, and should have a file name that is a short human readable description of the feature (using lowercase alphanumeric characters and dashes only). Try using the general area of the RFC as a prefix, e.g. `syntax-generic-functions.md` or `function-debug-info.md`. + +**Please make sure to add `rfc` label to PRs *before* creating them!** This makes sure that our automatic notifications work correctly. > Note: we currently don't accept community contributions for RFCs, although this will likely change in the future.