Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ Add new custom-composer-filename option #261

Open
wants to merge 3 commits into
base: v3
Choose a base branch
from

Conversation

badasukerubin
Copy link

@badasukerubin badasukerubin commented Sep 11, 2024

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

PR checklist

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • I have added tests to cover my changes.

@badasukerubin badasukerubin marked this pull request as ready for review September 12, 2024 12:21
@badasukerubin badasukerubin changed the title feat: custom-composer: composer_paths ✨ Add new custom-composer-filename option Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

composer.json based on environment
1 participant