feat: add root_marker input to support --root-marker flag#35
Merged
Conversation
Expose the --root-marker option through the GitHub Actions wrapper by adding a new optional root_marker input.
github-actions
bot
added
the
changelog/skip
babarot
added
kind/feature
Merged
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
1 participant
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.
What
Add a new optional
root_markerinput that passes--root-markerto thechanged-objectsCLI.root_markerinput toaction.yml(optional, default empty)INPUT_ROOT_MARKERhandling inentrypoint.shWhy
To expose the
--root-markeroption added inchanged-objectsthrough the GitHub Actions wrapper, allowing workflows to specify a file pattern (e.g.*.tf) that marks the root of a module directory. This enables Terraform workflows to resolve non-.tffile changes to the correct module root without custom shell logic.