Unify RFC Naming and Structure#138
Merged
Merged
Conversation
Contributor
|
Thanks very much for the PR - it helps a lot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In reference to #124 I restructured the RFCs to have unified naming scheme and title cases for each file. It also updates the Readme and template to explain
that schema.
Further more this PR contains an updated version of the generator script, which thanks to the new scheme will print each RFC at most once, as well as the updated result of that script.
However, this does not yet totally fix issue #124 as RFC #24 still doesn't show up. That would require a rewrite of that RFC (and potentially merge it with #20?), for which I am missing the background information on how that should be done.
This change is