@@ -462,33 +462,6 @@ steps:
462462If feeling kindly, please update [ mypy] ( https://github.com/python/mypy/blob/master/mypy/stubinfo.py )
463463for any stub obsoletions or removals.
464464
465- ## Maintainer guidelines
466-
467- The process for preparing and submitting changes also applies to
468- maintainers. This ensures high quality contributions and keeps
469- everybody on the same page. Avoid direct pushes to the repository.
470-
471- When reviewing pull requests, follow these guidelines:
472-
473- * Typing is hard. Try to be helpful and explain issues with the PR,
474- especially to new contributors.
475- * When reviewing auto-generated stubs, just scan for red flags and obvious
476- errors. Leave possible manual improvements for separate PRs.
477- * When reviewing large, hand-crafted PRs, you only need to look for red flags
478- and general issues, and do a few spot checks.
479- * Review smaller, hand-crafted PRs thoroughly.
480-
481- When merging pull requests, follow these guidelines:
482-
483- * Always wait for tests to pass before merging PRs.
484- * Use "[ Squash and merge] ( https://github.com/blog/2141-squash-your-commits ) " to merge PRs.
485- * Make sure the commit message is meaningful. For example, remove irrelevant
486- intermediate commit messages.
487- * The commit message for third-party stubs is used to generate the changelog.
488- It should be valid Markdown, be comprehensive, read like a changelog entry,
489- and assume that the reader has no access to the diff.
490- * Delete branches for merged PRs (by maintainers pushing to the main repo).
491-
492465### Marking PRs as "deferred"
493466
494467We sometimes use the [ "status: deferred" label] ( https://github.com/python/typeshed/labels/status%3A%20deferred )
@@ -500,25 +473,9 @@ external factor. Blockers can include:
500473- A dependency on a typing PEP that is still under consideration.
501474- A pending change in a related project, such as stub-uploader.
502475
503- PRs should only be marked as "deferred" if there is a clear path towards getting
504- the blocking issue resolved within a reasonable time frame. If a PR depends on
505- a more amorphous change, such as a type system change that has not yet reached
506- the PEP stage, it should instead be closed.
507-
508- Maintainers who add the "deferred" label should state clearly what exactly the
509- blocker is, usually with a link to an open issue in another project.
510-
511476### Closing stale PRs
512477
513478To keep the number of open PRs manageable, we may close PRs when they have been
514479open for too long. Specifically, we close open PRs that either have failures in CI,
515480serious merge conflicts or unaddressed feedback, and that have not seen any
516481activity in three months.
517-
518- We want to maintain a welcoming atmosphere for contributors, so use a friendly
519- message when closing the PR. Example message:
520-
521- Thanks for contributing! I'm closing this PR for now, because it still
522- <fails some tests OR has unresolved review feedback OR has a merge conflict>
523- after three months of inactivity. If you are still interested, please feel free to open
524- a new PR (or ping us to reopen this one).
0 commit comments