Repository navigation
Conversation
Explain collection event notifications and link the hook reference sections. Co-authored-by: Codex <noreply@openai.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The hook reference lists collection event notifications under Reporting hooks, but does not explain the distinction between reporting events to plugins and displaying results to users. This makes collection hooks such as
pytest_collectstartdifficult to find when browsing by session phase.Add an explanation of reporting hooks and reciprocal links between the Collection hooks and Reporting hooks sections. The explanation follows the maintainer guidance in #12658. This change addresses the remaining explanatory gap without moving hooks between categories.
Validation:
sphinx-build -j 2 -W --keep-going -b html doc/en doc/en/_build/htmlon Python 3.12; the build succeeded.git diff --checkpassed.Prepared with Codex assistance and reviewed by the submitting contributor. The commit includes a Co-authored-by trailer. This is a small documentation clarification; no runtime behavior changes.