-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[ci] allow flex to run in CI #17020
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
[ci] allow flex to run in CI #17020
Conversation
Flex is already allowed in the application (see https://github.com/symfony-tools/code-block-checker/blob/main/composer.json#L48). That should be enough, shouldn't it? |
It is allowed for that package https://github.com/symfony/symfony-docs/runs/7438798967?check_suite_focus=true shows CI failing due to the plugin not explicitly being allowed. EDIT a better example w/ CI failing because of |
Jesse, thanks for this fix too. |
Good hint @jrushlow. I think we should fix it their too (see symfony-tools/symfony-application#14). |
This PR was squashed before being merged into the 5.4 branch. Discussion ---------- Enable code blocks Revert 8f250a2 Revert fb505de from #17020 Tests were broken, see that example from #17098: ``` Run composer config --no-plugins allow-plugins.symfony/flex true Error: File "./composer.json" cannot be found in the current directory In ConfigCommand.php line 206: File "./composer.json" cannot be found in the current directory config [-g|--global] [-e|--editor] [-a|--auth] [--unset] [-l|--list] [-f|--file FILE] [--absolute] [-j|--json] [-m|--merge] [--append] [--source] [--] [<setting-key> [<setting-value>...]] Error: Process completed with exit code 1. ``` [full output](https://github.com/symfony/symfony-docs/runs/7640214086?check_suite_focus=true) It should not be necessary now that symfony-tools/symfony-application#14 has been merged. Commits ------- 7bff8b5 Enable code blocks
This PR was merged into the 4.4 branch. Discussion ---------- Fix CI by reverting symfony#17020 The CI is failing in symfony#16992 because of this, see https://github.com/symfony/symfony-docs/runs/7704382531?check_suite_focus=true. My guess if that it's now fixed upstream thanks to symfony-tools/symfony-application#14. Commits ------- 7c7c76e fix CI by reverting symfony#17020
* 4.4: fix CI by reverting symfony#17020
* 5.4: fix CI by reverting symfony#17020
* 6.0: fix CI by reverting symfony#17020
* 6.1: fix CI by reverting symfony#17020
Since Composer 2.3.9 unless you explicitly allow/disallow a plugin (flex in our case), an error is thrown (halts our CI run) before any tests are actually ran. (Code Blocks)