Skip to content

Display composer validation output#268

Open
defunctl wants to merge 2 commits intoramsey:v3from
defunctl:v3
Open

Display composer validation output#268
defunctl wants to merge 2 commits intoramsey:v3from
defunctl:v3

Conversation

@defunctl
Copy link
Copy Markdown

Description

Currently, if composer validate fails, you don't actually know why. This displays the error message.

Motivation and context

Not an exact fix for this, but at least it would tell the user what went wrong: #250

How has this been tested?

I ran it in my private GitHub repo.

Before:
image

After:
image

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.

@defunctl defunctl requested a review from ramsey as a code owner April 30, 2025 21:29
@ramsey
Copy link
Copy Markdown
Owner

ramsey commented May 3, 2025

Please check the test failures. I can help with the Bats tests, if needed—just let me know.

@llaville
Copy link
Copy Markdown

llaville commented Jul 23, 2025

I don't know context of @defunctl workflow run, but I would like to share my experience here because I cause a same error messages as show by his before screenshots.

My workflow release.yml install a repository with my fork of at least one dependency.

After many tests, I realized that my context is reusable worflows and I don't PASS it as expected.

See Official Documentation that save me : https://docs.github.com/en/actions/how-tos/sharing-automations/reuse-workflows#using-inputs-and-secrets-in-a-reusable-workflow

I.e: llaville/graph-uml@3bd38bb

@ramsey Perharps a NOTE on documentation about such context will help future users that could run in trouble

composer_auth_empty

This issue (screenshot) also raised when you define a COMPOSER_AUTH with an empty content (secret variable is not defined or empty)

                name: Install Composer dependencies
                uses: ramsey/composer-install@v3
                with:
                    composer-options: "--prefer-dist"
                env: # https://github.com/ramsey/composer-install?tab=readme-ov-file#fork-and-private-repositories
                    COMPOSER_AUTH: '{"github-oauth": {"github.com": "${{ secrets.COMPOSER_AUTH }}"}}'

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.

3 participants