-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Draft 2.0 discussion #710
Comments
Thanks Coraline for your hard work! I appreciate you list the differences between the two versions. I wonder if there is a way to see a git diff (if that\ would be useful at all)? |
Hi Coraline, the link to the latest version of the CoC provided in the attribution section is broken. It's caused by the use of underscores instead of dashes in the markdown file name. I'm unsure if it's more appropriate to correct the link, or to change the file name, so I thought I should point it out to you. Thanks! |
Oh, thanks for finding this! I didn’t realize that I changed from code-of-conduct to code_of_conduct in 2.0.
Fixed!
… On Nov 13, 2019, at 4:49 AM, Nithiya Streethran ***@***.***> wrote:
Hi Coraline, the link to the latest version of the CoC provided in the attribution section <https://www.contributor-covenant.org/version/2/0/code_of_conduct#attribution> is broken. It's caused by the use of underscores instead of dashes in the markdown file name. I'm unsure if it's more appropriate to correct the link, or to change the file name, so I thought I should point it out to you. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#710>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFODE6H7E53RVXJ6LOCF3QTPLURANCNFSM4I3AZTGA>.
|
Is v2.0 released? |
Great call. I updated the badge, but the translations will update with each 2.0 translation. Thanks! |
nice @CoralineAda about the badge, you updated 1 of 2.
update it to:
|
Oops, fixed! |
Please use this thread to discuss the draft of Contributor Covenant 2.0
(#709)
The text was updated successfully, but these errors were encountered: