feat: add input for module path #15
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
yann-soubeyrand
force-pushed
the
feat/add-module-path-input
branch
4 times, most recently
from
fb06842
to
35d232b
Compare
Signed-off-by: Yann Soubeyrand <[email protected]>
yann-soubeyrand
force-pushed
the
feat/add-module-path-input
branch
from
35d232b
to
92b946e
Compare
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.
Description
This pull request adds a new
module-pathinput to the action to support Dagger modules located elsewhere than in the current working directory.Motivation
When testing Daggerverse repositories containing several Dagger modules, one can use a GitHub Actions job with a matrix strategy to test each module individually. In this case, it’s necessary to be able to pass the module path to this action.
Linked issues
Checklist
This pull request:
If applicable, I’ve added the required tests.
If applicable, I’ve done the necessary documentation changes.
I’m legally entitled to submit this pull request and I’ve signed off all my commits to certify that my contribution conforms to the Developer Certificate of Origin (DCO).