You've already forked oncall
mirror of
https://github.com/linkedin/oncall.git
synced 2025-12-03 23:59:25 +02:00
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
|
Contribution Agreement
|
||
|
|
======================
|
||
|
|
|
||
|
|
As a contributor, you represent that the code you submit is your
|
||
|
|
original work or that of your employer (in which case you represent you
|
||
|
|
have the right to bind your employer). By submitting code, you (and, if
|
||
|
|
applicable, your employer) are licensing the submitted code to LinkedIn
|
||
|
|
and the open source community subject to the BSD 2-Clause license.
|
||
|
|
|
||
|
|
Responsible Disclosure of Security Vulnerabilities
|
||
|
|
==================================================
|
||
|
|
|
||
|
|
Please do not file reports on Github for security issues.
|
||
|
|
Please review the guidelines on at (link to more info).
|
||
|
|
Reports should be encrypted using PGP (link to PGP key) and sent to
|
||
|
|
security@linkedin.com preferably with the title "Github linkedin/<project> - <short summary>".
|
||
|
|
|
||
|
|
Tips for Getting Your Pull Request Accepted
|
||
|
|
===========================================
|
||
|
|
|
||
|
|
*Note: These are suggestions. Customize as needed.*
|
||
|
|
|
||
|
|
1. Make sure all new features are tested and the tests pass.
|
||
|
|
2. Bug fixes must include a test case demonstrating the error that it fixes.
|
||
|
|
3. Open an issue first and seek advice for your change before submitting
|
||
|
|
a pull request. Large features which have never been discussed are
|
||
|
|
unlikely to be accepted. **You have been warned.**
|