-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change MooseDocs CIVET mergeresults command defaults and add extension documentation #29566
base: next
Are you sure you want to change the base?
Conversation
Job Documentation, step Docs: sync website on e6b16ef wanted to post the following: View the site here This comment will be updated on new commits. |
Job Coverage, step Generate coverage on e6b16ef wanted to post the following: Framework coverageCoverage did not change Modules coverageCoverage did not change Full coverage reportsReports
This comment will be updated on new commits. |
MooseDocs.extensions.civet is not active in Mastodon's config.yml Refs idaholab/moose#29566
MooseDocs.extensions.civet is not active in Mastodon's config.yml Refs idaholab/moose#29566
MooseDocs.extensions.civet is not active in Mastodon's config.yml Refs idaholab/moose#29566
Job Documentation controlled apps on e6b16ef : invalidated by @cticenhour Griffin and Sockeye have been patched. |
Job Documentation public apps on e6b16ef : invalidated by @cticenhour Mastodon has been patched. |
The command will now always look to the current git commit SHA to determine the linked CI results by default. The old behavior is available using use_current_hash=False in the command. This commit also adds documentation for MooseDocs CIVET extension Refs idaholab#29565
Some apps do not have this extension enabled
e6b16ef
to
70ad6e7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unit tests an option?
@loganharbour Yeah, I can add one. |
Closes #29565
@gambka I discovered this while testing with your BISON branch. This should make the output of
!civet mergeresults
consistent for the release versions of BISON docs (or any older version of the docs built locally) by default.