-
Notifications
You must be signed in to change notification settings - Fork 44.4k
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
Added Contributing.md file #250
Added Contributing.md file #250
Conversation
@Torantulino can we make this fairly high priority, but also add in contribution guidelines on what kind of code styling/basic standards we want? |
``` | ||
git checkout -b "branch-name" | ||
``` | ||
4. Make your changes to the code or documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4. Make your changes to the code or documentation. | |
4. Make your changes to the code or documentation. | |
**Ensure each commit is small and addresses a SINGLE issue.** PRs with commits that sneak in extra tweaks will likely be rejected. |
``` | ||
git add . | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or, if using Git in VS-Code, select specific lines of code and commit them. | |
10. Select the branch you just pushed to and the branch you want to merge into on the original repository. | ||
|
||
11. Add a description of your changes and click the "Create pull request" button. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Be as clear, descriptive and specific as possible. | |
- Use markdown formatting for a clear and well written post. | |
Added Contributing.md file
No description provided.