Explain how security issues should be reported (#1898)

This commit is contained in:
Matt Brictson 2017-06-18 20:51:57 -07:00 committed by GitHub
parent 91321a0b9f
commit d1d6b5eedc
2 changed files with 4 additions and 0 deletions

View File

@ -41,6 +41,8 @@ Also include in your report:
If you are an experienced Ruby programmer, take a few minutes to get the Capistrano test suite running (see [DEVELOPMENT.md][]), and do what you can to get a test case written that fails. *This will be a huge help!*
If you think you may have discovered a security vulnerability in Capistrano, do not open a GitHub issue. Instead, please send a report to <security@capistranorb.com>.
## Requesting new features or improvements
Capistrano continues to improve thanks to people like you! Feel free to open a GitHub issue for any or all of these ideas:

View File

@ -186,6 +186,8 @@ Related GitHub repositories:
GitHub issues are for bug reports and feature requests. Please refer to the [CONTRIBUTING](CONTRIBUTING.md) document for guidelines on submitting GitHub issues.
If you think you may have discovered a security vulnerability in Capistrano, do not open a GitHub issue. Instead, please send a report to <security@capistranorb.com>.
## How to contribute
Contributions to Capistrano, in the form of code, documentation or idea, are gladly accepted. Read the [DEVELOPMENT](DEVELOPMENT.md) document to learn how to hack on Capistrano's code, run the tests, and contribute your first pull request.