feat [close #105]: Add property to decide wether to add includes per stage #129
Conversation
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
mirkobrombin
approved these changes
Dec 19, 2024
taukakao
reviewed
Dec 19, 2024
Member
taukakao
left a comment
taukakao
left a comment
There was a problem hiding this comment.
Just curious, why was this approach chosen instead of just checking if the path exists?
Contributor
Author
|
This is per stage, a user may want to include it during the testing stage but not the building stage, just checking if the directory exists wouldn't help |
Member
|
I see, interesting. But yeah, makes sense to me. |
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.
Adds a new property
addincludeswhich lets the user decide if a stage should include theincludes.containercloses #105