Rework the ReviewRequestApprovalHook docs for better flow and guidance.
Review Request #14757 — Created Jan. 1, 2026 and updated
The
ReviewRequestApprovalHookdocs were pretty old and did little to
communicate the expectations of the hook. The very first sentence said
these were new in Review Board 2.0.This change reworks the docs to clearly describe what approval state is
for and where it's used, the execution and chaining model of these
hooks, the signature ofis_approved()methods, examples, and best
practices.Typing and docs for the affected codepaths have been updated as well to
reflect what's shown in the guide and to link back to it.
Built the docs and checked the references/links on all affected code.
Ran content through ChatGPT for analysis and suggestions.
| Summary | ID |
|---|---|
| b54c07f84ae72a7a9f244a934b4d621c96577894 |
| Description | From | Last Updated |
|---|---|---|
|
This reads a little bit awkward. The review request isn't a user, the review request author (or submitter) is a … |
|
|
|
Based on the docstring, this should be bool | tuple[bool, str | None] (str -> bool) |
|
|
|
Here we could add "... pre-receive hooks (for example git-hook-check-approval)" |
|
|
|
Can we link to relevant docs for any of these items? |
|
|
|
This seems slightly more indented than it should be. |
|
- Change Summary:
-
- Fixed an awkwardly-worded comment in an example.
- Fixed a bad return type in the hook.
- Commits:
-
Summary ID e16867a5bb3c4853e5f204d8fe9a5ae373120e8e 9552ba8a5d3f866120211119e82c8d7660bbc0b2
Checks run (2 succeeded)
- Change Summary:
-
Added links to the Extensions and Integrations page when listing some places where this hook is useful.
- Commits:
-
Summary ID 9552ba8a5d3f866120211119e82c8d7660bbc0b2 8b0ae7ee71e872a72f6bd6a9281c1bf1ceb20eb6