11# How to Contribute
22
33We'd love to accept your patches and contributions to this project.
4- We do have some guidelines to follow, covered in this document, but don't
4+ We do have some guidelines to follow, covered in this document, but don't
55worry about (or expect to) get everything right the first time!
6- Create a pull request and we'll nudge you in the right direction. Please also
6+ Create a pull request and we'll nudge you in the right direction. Please also
77note that we have a [ code of conduct] ( CODE_OF_CONDUCT.md ) to make Cirq an
88open and welcoming environment.
99
@@ -83,7 +83,7 @@ on setting up your local development environment.
8383
8484# # Code Testing Standards
8585
86- When a pull request is created or updated, various automatic checks will
86+ When a pull request is created or updated, various automatic checks will
8787run to ensure that the change won' t break Cirq and meets our coding standards.
8888
8989Cirq contains a continuous integration tool to verify testing. See our
@@ -94,36 +94,36 @@ Please be aware of the following code standards that will be applied to any
9494new changes.
9595
9696- **Tests**.
97- Existing tests must continue to pass (or be updated) when new changes are
98- introduced. We use [pytest](https://docs.pytest.org/en/latest/) to run our
97+ Existing tests must continue to pass (or be updated) when new changes are
98+ introduced. We use [pytest](https://docs.pytest.org/en/latest/) to run our
9999tests.
100100- **Coverage**.
101101Code should be covered by tests.
102- We use [pytest-cov](https://pytest-cov.readthedocs.io/en/latest/) to compute
102+ We use [pytest-cov](https://pytest-cov.readthedocs.io/en/latest/) to compute
103103coverage, and custom tooling to filter down the output to only include new or
104- changed code. We don' t require 100% coverage, but any uncovered code must
105- be annotated with ` # coverage: ignore ` . To ignore coverage of a single line,
106- place ` # coverage: ignore ` at the end of the line. To ignore coverage for
107- an entire block, start the block with a ` # coverage: ignore ` comment on its
104+ changed code. We don' t require 100% coverage, but any uncovered code must
105+ be annotated with ` # pragma: no cover ` . To ignore coverage of a single line,
106+ place ` # pragma: no cover ` at the end of the line. To ignore coverage for
107+ an entire block, start the block with a ` # pragma: no cover ` comment on its
108108own line.
109109- ** Lint** .
110- Code should meet common style standards for python and be free of error-prone
110+ Code should meet common style standards for python and be free of error-prone
111111constructs. We use [pylint](https://www.pylint.org/) to check for lint.
112- To see which lint checks we enforce, see the
112+ To see which lint checks we enforce, see the
113113[dev_tools/conf/.pylintrc](dev_tools/conf/.pylintrc) file. When pylint produces
114- a false positive, it can be squashed with annotations like
114+ a false positive, it can be squashed with annotations like
115115` # pylint: disable=unused-import` .
116116- ** Types** .
117117Code should have [type annotations](https://www.python.org/dev/peps/pep-0484/).
118118We use [mypy](http://mypy-lang.org/) to check that type annotations are correct.
119- When type checking produces a false positive, it can be ignored with
119+ When type checking produces a false positive, it can be ignored with
120120annotations like ` # type: ignore` .
121121
122122# # Request For Comment Process for New Major Features
123123
124- For larger contributions that will benefit from design reviews, please use the
124+ For larger contributions that will benefit from design reviews, please use the
125125[Request for Comment](docs/dev/rfc_process.md) process.
126126
127- # # Developing notebooks
127+ # # Developing notebooks
128128
129- Please refer to our [notebooks guide](docs/dev/notebooks.md) on how to develop iPython notebooks for documentation.
129+ Please refer to our [notebooks guide](docs/dev/notebooks.md) on how to develop iPython notebooks for documentation.
0 commit comments