DOC: contributing guide #1223
Merged
DOC: contributing guide #1223
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
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.
Per #1222 (comment), started a contributing guide so there'd be a place to document stuff like testing. Feel free to adopt to your culture and community goals.
I mostly stuck to the readme but made everything a
pipcommand 'cause terrible things seem to happen when stuff is mixed & I figure more experienced contributors will just use whatever they're used to.Figured you all didn't want to maintain copy of the github workflow, so linked out to github's contributing guide for anything that wasn't specific to your workflow.