This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
feat: add initial lula lint in OSCAL creation and lula lint action #665
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
mjnagel
reviewed
Jan 16, 2024
|
@mjnagel the lula-lint action would catch any changes to the OSCAL that could happen outside of the component generator. Its not a necessity where its included in the in the component generator portion. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Added initial Lula Lint Action.
Checkouts code, setups Lula, and Lints the OSCAL file to ensure it is a schema compliant file.
Only triggers on changes to the OSCAL file.
Added Lula Lint inside of OSCAL generation to lint files at time of creation. This covers scenarios where OSCAL is created in CI from Component Generator or out of line updates.