kyy/swagger-ui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Github link

Browse Source
This commit is contained in:
Kyle Shockey
2017-07-24 23:31:54 -07:00
parent d95c6523ff
commit 09d3f5ad6c
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@@ -38,14 +38,14 @@ If there's an issue filed that you're addressing in your branch, include the iss
- Use the imperative mood in your subject lines, as if you were giving the code an order in your subject line. - Use the imperative mood in your subject lines, as if you were giving the code an order in your subject line.
- This mimics what Git does for you automatically: "Merge develop", "Revert f570ffc", etc - This mimics what Git does for you automatically: "Merge develop", "Revert f570ffc", etc
- Simple trick... your subject line should complete this sentence: `If applied, this commit will [your subject line].` - Simple trick... your subject line should complete this sentence: `If applied, this commit will [your subject line].`
- Don't use [magic GitHub words]() in your commits to close issues - do that in the pull request for your code instead. - Don't use [magic GitHub words](https://help.github.com/articles/closing-issues-using-keywords/) in your commits to close issues - do that in the pull request for your code instead.
_Adapted from [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/#seven-rules)._ _Adapted from [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/#seven-rules)._
#### Making pull requests #### Making pull requests
- **Do** summarize your changes in the PR body. If in doubt, write a bullet-point list titled `This PR does the following:`. - **Do** summarize your changes in the PR body. If in doubt, write a bullet-point list titled `This PR does the following:`.
- **Do** include references to issues that your PR solves, and use [magic GitHub words]() to close those issues automatically when your PR is merged. - **Do** include references to issues that your PR solves, and use [magic GitHub words](https://help.github.com/articles/closing-issues-using-keywords/) to close those issues automatically when your PR is merged.
- **Do** include tests that cover new or changed functionality. - **Do** include tests that cover new or changed functionality.
- **Do** be careful to follow our ESLint style rules. We recommend installing an ESLint plugin if you use a graphical code editor. - **Do** be careful to follow our ESLint style rules. We recommend installing an ESLint plugin if you use a graphical code editor.
- **Do** make sure that tests and the linter are passing by running `npm test` locally, otherwise we can't merge your pull request. - **Do** make sure that tests and the linter are passing by running `npm test` locally, otherwise we can't merge your pull request.