Skip to content

Mention typo fixes and large PRs#1782

Open
johnslavik wants to merge 4 commits intopython:mainfrom
johnslavik:gh-1448-typo-fixes-section
Open

Mention typo fixes and large PRs#1782
johnslavik wants to merge 4 commits intopython:mainfrom
johnslavik:gh-1448-typo-fixes-section

Conversation

@johnslavik
Copy link
Copy Markdown
Member

No description provided.

Add guidance on keeping typo-fix PRs small and focused, listing
appropriate directories (Doc/, Misc/, Misc/NEWS.d/) and noting
that large sweeping PRs may be closed.
- Clarify which directories are appropriate for typo fixes
- Encourage small, focused PRs to reduce reviewer notification burden
- Explicitly note that large PRs or PRs outside listed directories
  may be closed with a reference to this section
@johnslavik johnslavik requested review from hugovk and willingc April 15, 2026 10:09
@johnslavik johnslavik self-assigned this Apr 15, 2026
@read-the-docs-community
Copy link
Copy Markdown

read-the-docs-community bot commented Apr 15, 2026

Copy link
Copy Markdown
Collaborator

@willingc willingc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @johnslavik. Please leave a brief note in the PR submission message what prompted you to propose these devguide changes. I do think that this is a useful addition. ☀️

#. **Keep your pull request focused and small.** A pull request should address
one issue or add one feature. Combining multiple unrelated changes makes a
pull request harder to review and increases the number of people notified
unnecessarily. When in doubt, split into separate pull requests.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
unnecessarily. When in doubt, split into separate pull requests.
unnecessarily.

Typo fixes
==========

Fixing typos and grammatical errors in documentation is a welcome
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Fixing typos and grammatical errors in documentation is a welcome
Fixing typos and grammatical errors in documentation is a

Comment on lines +275 to +285
places for such fixes are:

* The ``Doc/`` directory (end-user documentation)
* Internal documentation, such as files in ``Misc/``
* News entries under ``Misc/NEWS.d/``

Keep typo-fix PRs **small and focused**, ideally limited to one file or a
small set of closely related files. Large PRs that touch many unrelated files
notify a large number of reviewers unnecessarily and are harder to review.
Large typo-fix PRs, or PRs touching directories outside those listed above,
may be closed with a reference to this section.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
places for such fixes are:
* The ``Doc/`` directory (end-user documentation)
* Internal documentation, such as files in ``Misc/``
* News entries under ``Misc/NEWS.d/``
Keep typo-fix PRs **small and focused**, ideally limited to one file or a
small set of closely related files. Large PRs that touch many unrelated files
notify a large number of reviewers unnecessarily and are harder to review.
Large typo-fix PRs, or PRs touching directories outside those listed above,
may be closed with a reference to this section.
place for such fixes is the ``Doc/`` directory (end-user documentation).
Keep typo-fix PRs **small and focused**. Large PRs that touch many unrelated files
notify a large number of reviewers unnecessarily and are harder to review.
Large typo-fix PRs, or PRs touching directories outside those listed above,
may be closed with a reference to this section.

Copy link
Copy Markdown
Member

@StanFromIreland StanFromIreland Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO we can also include InternalDocs.

Comment on lines +275 to +285
places for such fixes are:

* The ``Doc/`` directory (end-user documentation)
* Internal documentation, such as files in ``Misc/``
* News entries under ``Misc/NEWS.d/``

Keep typo-fix PRs **small and focused**, ideally limited to one file or a
small set of closely related files. Large PRs that touch many unrelated files
notify a large number of reviewers unnecessarily and are harder to review.
Large typo-fix PRs, or PRs touching directories outside those listed above,
may be closed with a reference to this section.
Copy link
Copy Markdown
Member

@StanFromIreland StanFromIreland Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO we can also include InternalDocs.

<https://github.com/python/cpython/issues/126133#issuecomment-2460824052>`__.


.. _typo-fixes:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to reference the section somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants