Skip to content

Maintenance Mode and syde/phpcs #103

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

Merged
merged 2 commits into from
Jan 27, 2025
Merged

Maintenance Mode and syde/phpcs #103

merged 2 commits into from
Jan 27, 2025

Conversation

tfrommen
Copy link
Member

@tfrommen tfrommen commented Dec 23, 2024

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Inform users about shifting to maintenance mode, and the new syde/phpcs package.

What is the current behavior? (You can also link to an open issue here)

Users do not know about maintenance mode, nor syde/phpcs.

What is the new behavior (if this is a feature change)?

The README informs about the package being in maintenance mode, and recommends migrating to the new syde/phpcs package. Composer will suggest using the package, too.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Signed-off-by: Thorsten Frommen <[email protected]>
@tfrommen
Copy link
Member Author

@Chrico @gmazzap @antonioeatgoat with the first stable release of syde/phpcs, I feel this is good to go now.

I am thinking this would be a patch-level release, 2.0.1, so many people will get this information (also the Composer-based suggestion) relatively soon. Do you agree?

@tfrommen tfrommen merged commit 03c4de3 into version/2 Jan 27, 2025
17 checks passed
@tfrommen tfrommen deleted the maintenance-mode branch January 27, 2025 19:39
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