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

CS/check thresholds: require exact match for thresholds #164

Merged
merged 1 commit into from
Apr 6, 2024

Conversation

jrfnl
Copy link
Contributor

@jrfnl jrfnl commented Apr 6, 2024

This changes the implementation of the coding standards threshold check to require that both the YOASTCS_THRESHOLD_ERRORS environment variable, as well as the YOASTCS_THRESHOLD_WARNINGS environment variable match the current status exactly.

This prevents PR A fixing some issues and forgetting to update the threshold, which then would allow PR B to introduce new issues.

Note: WHIP currently doesn't use the threshold check in CI as the package is "clean". This commit just makes sure that the threshold implementation is in line with that in other plugins for consistency.

This changes the implementation of the coding standards threshold check to require that both the `YOASTCS_THRESHOLD_ERRORS` environment variable, as well as the `YOASTCS_THRESHOLD_WARNINGS` environment variable match the current status exactly.

This prevents PR A fixing some issues and forgetting to update the threshold, which then would allow PR B to introduce new issues.
@jrfnl jrfnl added this to the 2.x Next Release milestone Apr 6, 2024
@jrfnl jrfnl merged commit a286169 into main Apr 6, 2024
2 checks passed
@jrfnl jrfnl deleted the feature/composer-actions-update-threshold-check branch April 6, 2024 03:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant