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 class-leak to composer scripts #320

Conversation

maks-rafalko
Copy link
Contributor

  • to increase its visibility
  • to fix errors locally instead of seeing on GH Actions

Originally found here: #319 (comment)

- to increase its visibility
- to fix errors locally instead of seeing on GH Actions
Copy link
Contributor

@staabm staabm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like

@samsonasik samsonasik merged commit a56b646 into rectorphp:main Apr 3, 2024
5 checks passed
@samsonasik
Copy link
Member

Thank you @maks-rafalko

@maks-rafalko maks-rafalko deleted the feature/add-class-leak-to-composer-scripts branch April 3, 2024 15:33
maks-rafalko added a commit to maks-rafalko/rector-phpunit that referenced this pull request Apr 8, 2024
…d line on GH action

This is a follow up for rectorphp#320 and related to rectorphp#319 (comment)

Instead of duplicating command line on `code_analysis.yaml` action file, we can just reuse `composer class-leak` from `composer.json`.

Each time `composer class-leak` is updated, it will be automatically used on GH Action, so no need to update duplicated command twice.

Without it, we will have an issue when we start addign `--skip-type` for `vendor/bin/class-leak` in `code_analysis.yaml`. The same `--skip-type` would be added to 2 places without this PR.
TomasVotruba pushed a commit that referenced this pull request Apr 8, 2024
…d line on GH action (#323)

This is a follow up for #320 and related to #319 (comment)

Instead of duplicating command line on `code_analysis.yaml` action file, we can just reuse `composer class-leak` from `composer.json`.

Each time `composer class-leak` is updated, it will be automatically used on GH Action, so no need to update duplicated command twice.

Without it, we will have an issue when we start addign `--skip-type` for `vendor/bin/class-leak` in `code_analysis.yaml`. The same `--skip-type` would be added to 2 places without this PR.
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.

None yet

3 participants