#366 compliance: find solution for updated articles published <2023#226
Open
Lorenzovagliano wants to merge 1 commit into
Conversation
7f47b76 to
3103fe0
Compare
54fc670 to
ac320fc
Compare
…termine whether and Article is being updated. If so, it treats articles published before 2023 normally rather than marking them as compliant. signed-off-by: vaglianolorenzo@gmail.com
ac320fc to
898159a
Compare
This file contains hidden or 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
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.
Made it so that compliance_checks receives a parameter in order to determine whether an Article is being updated. If so, it treats articles published before 2023 normally rather than marking them as compliant.
#366 (cern-sis/issues-scoap3#366)