Implement external impact reporting for changed files without build list #570
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
list Signed-off-by: Dennis Behm <[email protected]>
M-DLB
reviewed
Nov 25, 2024
Co-authored-by: Mathieu Dalbin <[email protected]>
M-DLB
approved these changes
Nov 26, 2024
dennis-behm
deleted the
feature/533-enable-report-external-impacts-also-for-builds-that-dont-contain-any-buildable-files
branch
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 is adding the third condition to implement the case if no files are on the build list (potentially) but the build had identified changed file.
This is useful for scenarios with just a copybook change in a shared copybook repo that does not have buildable files..