Skip to content

chore: check if fabbot is correctly working #2014

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

Closed
wants to merge 1 commit into from

Conversation

Kocal
Copy link
Member

@Kocal Kocal commented Jul 30, 2024

Q A
Bug fix? yes/no
New feature? yes/no
Issues Fix #...
License MIT

PR opened for Fabien.

Following #1996, we need to understand if something is wrong with fabbot or not.
⚠️ This PR should not be merged!

@carsonbot carsonbot added Bug Bug Fix Feature New Feature Status: Needs Review Needs to be reviewed labels Jul 30, 2024
@javiereguiluz
Copy link
Member

fabbot seems to be working ... so maybe it was a temporary error?

@Kocal
Copy link
Member Author

Kocal commented Jul 30, 2024

fabbot is green when it's supposed to be red, the code here is not valid (run PHP-CS-Fixer locally and see the diff).

But I'm already seeing this problem with Fabien!
This afternoon he fixed the issue Unable to parse the PHP CS Fixer configuration: %sSandboxed code attempted to call non-whitelisted class: PhpCsFixer\\Runner\\Parallel\\ParallelConfigFactory, but there is still more one issue.

@smnandre
Copy link
Member

(side topic: if we also could make a global pass with fabbot, to fix all the exceptions format at once, that'd be great)

@Kocal Kocal mentioned this pull request Aug 17, 2024
kbond added a commit that referenced this pull request Aug 20, 2024
This PR was merged into the 2.x branch.

Discussion
----------

chore: run PHP-CS-Fixer

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

<!--
Replace this notice by a description of your feature/bugfix.
This will help reviewers and should be a good start for the documentation.

Additionally (see https://symfony.com/releases):
 - Always add tests and ensure they pass.
 - For new features, provide some code snippets to help understand usage.
 - Features and deprecations must be submitted against branch main.
 - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
 - Never break backward compatibility (see https://symfony.com/bc).
-->

Fabbot still misses our PHP-CS-Fixer configuration (tracked in #2014) :(

Commits
-------

1420976 chore: run PHP-CS-Fixer
@Kocal
Copy link
Member Author

Kocal commented Aug 26, 2024

Okay, here fabbot is working as expected:
image

Closing for now, let's observe other PR 👀

@Kocal Kocal closed this Aug 26, 2024
@Kocal Kocal mentioned this pull request May 31, 2025
Kocal added a commit that referenced this pull request May 31, 2025
This PR was squashed before being merged into the 2.x branch.

Discussion
----------

[CI] Re-add PHP-CS-Fixer

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Docs?         | no <!-- required for new features -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

<!--
Replace this notice by a description of your feature/bugfix.
This will help reviewers and should be a good start for the documentation.

Additionally (see https://symfony.com/releases):
 - Always add tests and ensure they pass.
 - For new features, provide some code snippets to help understand usage.
 - Features and deprecations must be submitted against branch main.
 - Update/add documentation as required (we can help!)
 - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
 - Never break backward compatibility (see https://symfony.com/bc).
-->

Follow #2802, #2074, #2014 and more.

I feel like Fabbot **only runs on modified files** for a given PR, but sometimes it does not really help (e.g.: if you untouched files contain old references to a deleted class).

This behavior is understandable for symfony/symfony, which contains a tons of code and is super active, but that's not the case symfony/ux, we have very less code and less activity.

**EDIT:** Well, I'm still not sure... PHP-CS-Fixer is showing me fixes for `src/LiveComponent/src/Util/TypeHelper.php`, added in #2778, but it was totally ignored by Fabbot... 😫

So, I suggest to re-add PHP-CS-Fixer run in the CI to ensure all files are correctly CS-fixed.

Commits
-------

1ab48b6 [CI] Re-add PHP-CS-Fixer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug Fix Feature New Feature Status: Needs Review Needs to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants