Rearrange RBTools documentation a bit.
Review Request #14348 — Created Feb. 14, 2025 and updated
This change rearranges the RBTools documentation to try to simplify some
things:
-
Moved info about .reviewboardrc files to the main "configuration"
page, and clarified where different files are loaded from and in what
priority order. -
Updated repo configuration page to emphasize why a .reviewboardrc file
is a good idea and moved the alternative methods up next to that so
it's clear what they're for. - Moved the
ENABLE_PROXY
documentation from repository config to user
config. - Split the docs about aliases out into its own page.
- On the main index page, simplified the "Getting Started" section to be
install, configure, use. - Moved links for authentication and TFS into the "Common RBTools
workflows" section.
Built docs and checked the results.
Summary | ID |
---|---|
fb1970dbc1e9139ddfafef22255cc2214639ea2b |
Description | From | Last Updated | ||
---|---|---|---|---|
Can we reference the config for ALIASES? If there's a ref name for that. |
|
|||
I think for each of these, we should provide a concrete example to drive it home. It's otherwise a bit … |
|
|||
Extra blank line at the end of the file. |
|
|||
I think the parsing bit might be good as an important admonition. |
|
|||
This and the section below should be in Title Case, to match other sections. |
|
|||
Maybe "If for some reason you can't ...", to help this feel a bit more plain-spoken for readers. |
|
|||
There are no open issues |
-
-
-
I think for each of these, we should provide a concrete example to drive it home. It's otherwise a bit unclear without already knowing about these topics.
I think it may also be worth splitting up the paragraph into each main point (e.g., System Command Aliases could explain how they're set, then that they're flexible/dangerous, and then that everything is passed to the shell).
-
-
-
-