Skip to content

Conversation

@hugovk
Copy link
Member

@hugovk hugovk commented Nov 11, 2025

Promote the note to something that can be linked to, so we can easily share it with contributors who force push their PRs.

Add an extra sentence:

"When the PR is merged, everything will be squashed into a single commit."


📚 Documentation preview 📚: https://cpython-devguide--1687.org.readthedocs.build/

Copy link
Contributor

@itamaro itamaro left a comment

Choose a reason for hiding this comment

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

Nit comments:

  1. Maybe say "If the PR is merged" instead of "When ..."
  2. Consider qualifying the guidance with "for published PRs" (afaik it's ok to force push to draft PRs)

@hugovk
Copy link
Member Author

hugovk commented Nov 12, 2025

  1. Let's be positive and assume the PR will be merged :) It also matches the steps above.
  2. We still might want to incrementally review draft PRs, and no force-push helps avoid the mass-CODEOWNER-notification spam.

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.

2 participants