Added Implementation Guidance to maturity questions #4026
Merged
Conversation
This file contains 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
This field was added for CPG questions and is displayed in the "question extras" area if present.
jekuipers
approved these changes
Aug 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🗣 Description
CPG questions have implementation guidance defined for each answer option in each question. These values were formatted into HTML
lists and added to a new field, IMPLEMENTATION_GUIDES. The content is displayed in the question's "extras" component if present.- This PR has an informative and human-readable title.
- Changes are limited to a single goal - eschew scope creep!
- All future TODOs are captured in issues, which are referenced
- All relevant type-of-change labels have been added.
- I have read the CONTRIBUTING document.
- These code changes follow cisagov code standards.
- All relevant repo and/or project documentation has been updated
- Tests have been added and/or modified to cover the changes in this PR.
- All new and existing tests pass.
- Revert dependencies to default branches.
- Finalize version.
- Create a release.
💭 Motivation and context
🧪 Testing
✅ Pre-approval checklist
in code comments.
to reflect the changes in this PR.
✅ Pre-merge checklist
✅ Post-merge checklist