Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: RFC JSON formatting #840

Merged
merged 4 commits into from
Jun 12, 2024
Merged

Conversation

JamesKEbert
Copy link
Contributor

A couple of RFCs' JSON examples don't display properly in deployed site, so I ran a formatter over it to resolve the issues (the ```json= is the primary problem). The issue can be observed here: https://hyperledger.github.io/aries-rfcs/latest/features/0685-pickup-v2/#reference
Also updates RFC 0496 to be in ADOPTED category in mkdocs/index (#834)

Signed-off-by: James Ebert <jamesebert.k@gmail.com>
Signed-off-by: James Ebert <jamesebert.k@gmail.com>
@swcurran
Copy link
Member

swcurran commented Jun 5, 2024

I manually verified that the DCO is correct, despite the hung check. @ryjones — should we plan on going ahead with merges while the DCO check is stuck based on manual checking? What is the impact if we mistakenly think the DCO is correct and it is not?

@ryjones
Copy link
Contributor

ryjones commented Jun 5, 2024

@swcurran you should add this file in all of your repos

@swcurran
Copy link
Member

swcurran commented Jun 7, 2024

@JamesKEbert could you push some other commit to trigger the running of the DCO check? It should go then...

Signed-off-by: James Ebert <jamesebert.k@gmail.com>
@JamesKEbert
Copy link
Contributor Author

Done 👍

@TelegramSam TelegramSam merged commit d6d2fcf into hyperledger:main Jun 12, 2024
1 check passed
@JamesKEbert JamesKEbert deleted the fix/rfcJSON branch July 24, 2024 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants