|
a |
|
b/src/codellama-main/CONTRIBUTING.md |
|
|
1 |
# Contributing to Code Llama |
|
|
2 |
We want to make contributing to this project as easy and transparent as |
|
|
3 |
possible. |
|
|
4 |
|
|
|
5 |
## Pull Requests |
|
|
6 |
We actively welcome your pull requests to address bugs or inconsistencies but |
|
|
7 |
are not planning to add new features to the existing implementation. |
|
|
8 |
|
|
|
9 |
1. Fork the repo and create your branch from `main`. |
|
|
10 |
2. If you've added code that should be tested, add tests. |
|
|
11 |
3. If you've changed APIs, update the documentation. |
|
|
12 |
4. Ensure the test suite passes. |
|
|
13 |
5. Make sure your code lints. |
|
|
14 |
6. If you haven't already, complete the Contributor License Agreement ("CLA"). |
|
|
15 |
|
|
|
16 |
## Contributor License Agreement ("CLA") |
|
|
17 |
In order to accept your pull request, we need you to submit a CLA. You only need |
|
|
18 |
to do this once to work on any of Meta's open source projects. |
|
|
19 |
|
|
|
20 |
Complete your CLA here: <https://code.facebook.com/cla> |
|
|
21 |
|
|
|
22 |
## Issues |
|
|
23 |
We use GitHub issues to track public bugs. Please ensure your description is |
|
|
24 |
clear and has sufficient instructions to be able to reproduce the issue. |
|
|
25 |
|
|
|
26 |
Meta has a [bounty program](https://www.facebook.com/whitehat/) for the safe |
|
|
27 |
disclosure of security bugs. In those cases, please go through the process |
|
|
28 |
outlined on that page and do not file a public issue. |
|
|
29 |
|
|
|
30 |
## License |
|
|
31 |
By contributing to Code Llama, you agree that your contributions will be |
|
|
32 |
licensed under the LICENSE file in the root directory of this source tree. |