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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ When making changes, we try to follow the procedure below.
29
29
**Note: as of 2025-11-11, we are stillin the process of making `pcpostprocess` confirm to this rule.**
30
30
31
31
4.**Discuss code in a PR**
32
-
When your code is finished, or warrants discussion, create a [pull request](https://help.github.com/articles/about-pull-requests/) (PR).
32
+
When your code is finished, or warrants discussion, create a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) (PR).
33
33
In your branch, update the [Changelog](./CHANGELOG.md) with a link to this PR and a concise summary of the changes.
34
34
Finally, request a review of the code.
35
35
@@ -75,13 +75,13 @@ Isort is configured in [pyproject.toml](./pyproject.toml) under the section `too
Every method and every class should have a [docstring](https://www.python.org/dev/peps/pep-0257/) that describes in plain terms what it does, and what the expected input and output is.
81
79
82
80
Each docstring should start with a one-line explanation.
83
81
If more explanation is needed, this one-liner is followed by a blank line and more information in the following paragraphs.
0 commit comments