-
Notifications
You must be signed in to change notification settings - Fork 21
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
Adding val-1fa and val-1fb verification cases #22
Adding val-1fa and val-1fb verification cases #22
Conversation
0a57ee0
to
86a849c
Compare
Job Documentation on 1aed3b0 wanted to post the following: View the site here This comment will be updated on new commits. |
b34d2e0
to
227a3cc
Compare
@cticenhour It's still failing the documentation test although I made those updates in the yml file. |
I will take a closer look! Thanks for the heads up. |
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.
I can't make these suggestions in the general GitHub interface for some reason, but I would also make these changes:
diff --git a/doc/config.yml b/doc/config.yml
index 4832f50..59fb4ac 100644
--- a/doc/config.yml
+++ b/doc/config.yml
@@ -16,7 +16,7 @@ Extensions:
Documentation:
TMAP8-only Syntax: syntax/tmap_only.md
Complete Code Syntax: syntax/index.md
- Software Quality: sqa/index.md
+ Software Quality: /sqa/index.md
MooseDocs.extensions.appsyntax:
executable: ${ROOT_DIR}
includes:
diff --git a/doc/sqa_reports.yml b/doc/sqa_reports.yml
index cdcf159..bb89603 100644
--- a/doc/sqa_reports.yml
+++ b/doc/sqa_reports.yml
@@ -24,5 +24,6 @@ Requirements:
working_dirs:
- ${ROOT_DIR}/doc/content
- ${MOOSE_DIR}/framework/doc/content
+ - ${MOOSE_DIR}/modules/heat_conduction/doc/content
directories:
- ${ROOT_DIR}/test
All of these changes should fix both the SQA fail and the general documentation build fail. |
227a3cc
to
1aed3b0
Compare
@singhgp4321 Just checking - are you still pulling the verification documentation text from the older TMAP manual? It seems that branch protection rules are preventing me from merging this right now, even though I have write access. Pinging @lindsayad about it, though it might be a bit before he is in a position to respond. |
@cticenhour For this MR I wrote the documentation text, although I try to use what is already in the V&V report. |
Ref: #12