Adjust sonarcloud and integration test workflows #3259
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
Signed-off-by: Jamie Hale <jamiehalebc@gmail.com>
Signed-off-by: Jamie Hale <jamiehalebc@gmail.com>
|
|
The sonarcloud stuff needs to be merged into main before having effect. |
swcurran
approved these changes
Sep 26, 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.
This adjusts the soanrcloud to ignore coverage and duplication on the entire folders for the existing folders and scenarios.
Also runs integration tests when there is a pyproject.toml file change (during releases).
The security reports still generate for the entire repo. I don't think I can filter these. We could allow users to review or mark them as safe, or only scan the aries_cloudagent source code. I think it's ok to deal with this for now.
Also change to workflow to only run on hyperledger repo.