Add DOM Increment to In Progress section of README#161
Open
bryanburgers wants to merge 1 commit intoRESOStandards:mainfrom
Open
Add DOM Increment to In Progress section of README#161bryanburgers wants to merge 1 commit intoRESOStandards:mainfrom
bryanburgers wants to merge 1 commit intoRESOStandards:mainfrom
Conversation
bryanburgers
force-pushed
the
add-dom-increment-to-readme
branch
from
dc7ca33 to
0ee3a94
Compare
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
1 participant
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.
I'm not sure if this is the right process, but I think that RCP-51 qualifies as an in-progress proposal? So this PR adds it to that section of the README.
I know @SergioDelRioT4Bi was looking for RCP-51 last week and couldn't find it; having it on the README likely would have helped.
If I'm doing this wrong, let me know; I'd be happy to follow the correct process.