Skip to content

Conversation

@twm
Copy link
Contributor

@twm twm commented Nov 16, 2025

Trivial fix for this typo:

image

Thanks for submitting a PR, your contribution is really appreciated!

Here is a quick checklist that should be present in PRs.

  • Include documentation when adding new features.
  • Include new tests or update existing tests when applicable.
  • Allow maintainers to push and squash when merging my commits. Please uncheck this if you prefer to squash the commits yourself.

If this change fixes an issue, please:

  • Add text like closes #XYZW to the PR description and/or commits (where XYZW is the issue number). See the github docs for more information.

Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:

  • Create a new changelog file in the changelog folder, with a name like <ISSUE NUMBER>.<TYPE>.rst. See changelog/README.rst for details.

    Write sentences in the past or present tense, examples:

    • Improved verbose diff output with sequences.
    • Terminal summary statistics now use multiple colors.

    Also make sure to end the sentence with a ..

  • Add yourself to AUTHORS in alphabetical order.

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Nov 16, 2025
Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

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

This might not even need a change note..

@webknjaz webknjaz added skip news used on prs to opt out of the changelog requirement backport 9.0.x apply to PRs at any point; backports the changes to the 9.0.x branch labels Nov 16, 2025
@nicoddemus
Copy link
Member

Thanks @twm!

This might not even need a change note..

Indeed, removed it. What I suspect happens is that people open a PR, find that the chronographer build fails due to the lack of a change note, and believe they have to add it.

@nicoddemus nicoddemus marked this pull request as ready for review November 19, 2025 09:57
@nicoddemus nicoddemus enabled auto-merge (squash) November 19, 2025 09:57
@nicoddemus nicoddemus disabled auto-merge November 19, 2025 09:57
@nicoddemus nicoddemus enabled auto-merge (squash) November 19, 2025 09:57
@nicoddemus nicoddemus merged commit fd47511 into pytest-dev:main Nov 19, 2025
34 of 62 checks passed
@patchback
Copy link

patchback bot commented Nov 19, 2025

Backport to 9.0.x: 💚 backport PR created

✅ Backport PR branch: patchback/backports/9.0.x/fd47511afeb024d2fbad9257d1b44310672c6a0f/pr-13969

Backported as #13981

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Nov 19, 2025
webknjaz added a commit that referenced this pull request Nov 19, 2025
…d47511afeb024d2fbad9257d1b44310672c6a0f/pr-13969

[PR #13969/fd47511a backport][9.0.x] Fix a typo in the 9.0 changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 9.0.x apply to PRs at any point; backports the changes to the 9.0.x branch bot:chronographer:provided (automation) changelog entry is part of PR skip news used on prs to opt out of the changelog requirement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants