doc/wiki: Added generated CVAR descriptions. - #7902
Merged
Merged
Conversation
hzhou
reviewed
Jul 24, 2026
Currently in alphabetical order, generating script and instructions in Box
Add title, use h3 headers for CVAR names, backtick-quote function names, and organize entries into sections with a table of contents.
hzhou
approved these changes
Sep 30, 2026
Remove 8 stale entries not found in source. Add 16 missing CVARs with descriptions derived from source YAML declarations and code usage. Rebuild sections to restore correct groupings.
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
2 participants
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.
Provides website formatted descriptions of CVARs for the wiki.
Gives users who want to tinker and tune MPI a unified place for information. MPI_T_cvar_get_info works in code for runtime added CVARs but is terminal only, this provides a more stable second monitor lookup.
Currently in alphabetical order, generating script and instructions in Box
Pull Request Description
Author Checklist
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits are self-contained and do not do two things at once.
Commit message is of the form:
module: short descriptionCommit message explains what's in the commit.
Whitespace checker. Warnings test. Additional tests via comments.
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.