✨ Add new custom-composer-filename option #261
+315
−11
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
As discussed in #258 .
This adds a new
custom-composer-filename
option to the action, allowing for adding a custom composer filename, which can be helpful for using composer based on different environments.See: https://getcomposer.org/doc/03-cli.md#composer
Fixes #258.
Motivation and context
See: #258
How has this been tested?
Both unit tests as well as integration tests are included with the PR.
Types of changes
PR checklist