Draft
Conversation
Contributor
Author
|
@PhoenixWhitefire Thanks for finding. I'll get to it when I can |
Contributor
|
Sorting should be in order of most recently accepted to least recently accepted. Alphabetical ordering is just annoying and doesn't actually help us find recent RFCs. Like every time I need to check an RFC I go to the PRs tab and hope the branch wasn't deleted. |
Author
I'll look into that. Afaik Jekyll doesn't support that by default, would require some git integration |
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
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.


This PR:
(Implemented)to the links of RFCs that contain**Status**: ImplementedYou can preview this here.
Links don't work on this preview due to root URL differences.
The reason for these changes is the matter of RFC relevance, and to add a form of categorization.
(Should
(Implemented)be in the link or outside of it?)