You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
4
-
documentation, we greatly value feedback and contributions from our community.
3
+
Thank you for your interest in contributing to our project. Whether it's a bug
4
+
report, a new feature, an integration into existing long context libraries, or
5
+
additional documentation, we greatly value feedback and contributions from our
6
+
community.
5
7
6
-
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
7
-
information to effectively respond to your bug report or contribution.
8
+
Please read through this document before submitting any issues or pull requests
9
+
to ensure we have all the necessary information to effectively respond to your
10
+
bug report or contribution.
8
11
9
12
10
13
## Reporting Bugs/Feature Requests
11
14
12
15
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
13
16
14
-
When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
15
-
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
17
+
When filing an issue, please check existing open, or recently closed, issues to
18
+
make sure somebody else hasn't already reported the issue. Please try to include
19
+
as much information as you can. Details like these are incredibly useful:
16
20
17
21
* A reproducible test case or series of steps
18
22
* The version of our code being used
@@ -21,27 +25,38 @@ reported the issue. Please try to include as much information as you can. Detail
21
25
22
26
23
27
## Contributing via Pull Requests
24
-
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
28
+
Contributions via pull requests are much appreciated. Before sending us a pull
29
+
request, please ensure that:
25
30
26
31
1. You are working against the latest source on the *main* branch.
27
-
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
28
-
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
32
+
2. You check existing open, and recently merged, pull requests to make sure
33
+
someone else hasn't addressed the problem already. If the pull request is open,
34
+
feel free to add a comment to it, expressing your interest.
35
+
3. You open an issue to discuss any significant work - we would hate for your
36
+
time to be wasted.
29
37
30
38
To send us a pull request, please:
31
39
32
40
1. Fork the repository.
33
-
2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
34
-
3. Ensure local tests pass.
41
+
2. Modify the source; please focus on the specific change you are contributing.
42
+
If you also reformat all the code, it will be hard for us to focus on your
43
+
change.
44
+
3. Ensure that all local tests pass.
35
45
4. Commit to your fork using clear commit messages.
36
-
5. Send us a pull request, answering any default questions in the pull request interface.
37
-
6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
46
+
5. Send us a pull request, answering any default questions in the pull request
47
+
interface.
48
+
6. Pay attention to any automated CI failures reported in the pull request, and
49
+
stay involved in the conversation.
38
50
39
51
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
40
52
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
41
53
42
54
43
55
## Finding contributions to work on
44
-
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
56
+
Looking at the existing issues is a great way to find something to contribute
57
+
on. As our projects, by default, use the default GitHub issue labels
58
+
(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at
59
+
any 'help wanted' issues is a great place to start.
45
60
46
61
47
62
## Code of Conduct
@@ -51,9 +66,12 @@ opensource-codeofconduct@amazon.com with any additional questions or comments.
51
66
52
67
53
68
## Security issue notifications
54
-
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
69
+
If you discover a potential security issue in this project we ask that you notify
70
+
AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/).
71
+
Please do **not** create a public github issue.
55
72
56
73
57
74
## Licensing
58
75
59
-
See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
76
+
See the [LICENSE](./LICENSE) file for our project's licensing. We will ask you
0 commit comments