docs(contributing): update table of contents #1332
Merged
Conversation
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
alexander-akait
approved these changes
Mar 17, 2020
anshumanv
approved these changes
Mar 17, 2020
Member
Author
|
@evilebottnawi can I be a member of the organisation? |
|
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Member
|
@snitin315 It would be great if you fixed something or improved, not only docs. You could show yourself and other contributors could see your abilities |
Member
Author
Member
|
@snitin315 Good job! Let's start by inviting you in slack channel, please write me your email on sheo13666q@gmail . com |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What kind of change does this PR introduce?
updated CONTRIBUTING.md table-of-contents.
Did you add tests for your changes?
NA
If relevant, did you update the documentation?
yes
Summary
NA
Does this PR introduce a breaking change?
Other information
NA