Ensure checked-in RAL is consistent with generated RAL #68
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.
The goal is to enable git dependencies and lower the bar for contribution. See #65 for more information.
The PR builds on #67. To ensure the checked-in RAL code is consistent with what is auto-generated, we add a new CI job,
gen-ral
, which will generate the RAL and check for any file differences. If users are correctly modifying the RAL by editing theimxrtral.py
script, there should be no file differences between what is checked in and what is generated. But, if the user manually modifies a RAL source file, and it's not reflected inimxrtral.py
, the job fails.Note that this PR targets the
check-in-ral
branch, which is described by #67. If accepted, we should also feel comfortable accepting #67.Testing
gen-ral
job failed