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
- Follows the existing style of the code base (see Codestyle section).
8
+
- Has comments included as needed.
9
+
10
+
- A test case that demonstrates the previous flaw that now passes with
11
+
the included patch, or demonstrates the newly added feature.
12
+
- If it adds/changes a public API, it must also include documentation
13
+
for those changes.
14
+
- Must be appropriately licensed (Apache 2.0).
15
+
16
+
Reporting An Issue/Feature
17
+
--------------------------
18
+
First, check to see if there's an existing
19
+
`issue <https://github.com/boto/botocore/issues>`__/`pull requests <https://github.com/boto/botocore/pulls>`__ for the bug/feature.
20
+
21
+
If there isn't an existing issue there, please file an issue *first*. The
22
+
ideal report includes:
23
+
24
+
- A description of the problem/suggestion.
25
+
- How to recreate the bug.
26
+
- If relevant, including the versions of your:
27
+
28
+
- Python interpreter
29
+
- s3transfer
30
+
- Optionally of the other dependencies involved (e.g. Botocore)
31
+
32
+
- If possible, create a pull request with a (failing) test case
33
+
demonstrating what's wrong. This makes the process for fixing bugs
34
+
quicker & gets issues resolved sooner.
35
+
36
+
Codestyle
37
+
---------
38
+
This project uses flake8 to enforce codstyle requirements. We've codified this
39
+
process using a tool called `pre-commit <https://pre-commit.com/>`__. pre-commit
40
+
allows us to specify a config file with all tools required for code linting,
41
+
and surfaces either a git commit hook, or single command, for enforcing these.
42
+
43
+
To validate your PR prior to publishing, you can use the following
44
+
`installation guide <https://pre-commit.com/#install>`__ to setup pre-commit.
45
+
46
+
If you don't want to use the git commit hook, you can run the below command
47
+
to automatically perform the codestyle validation:
48
+
49
+
.. code-block:: bash
50
+
51
+
$ pre-commit run
52
+
53
+
This will automatically perform simple updates (such as white space clean up)
54
+
and provide a list of any failing flake8 checks. After these are addressed,
55
+
you can commit the changes prior to publishing the PR.
56
+
These checks are also included in our CI setup under the "Lint" workflow which will provide output on Github for anything missed locally.
0 commit comments