-
Notifications
You must be signed in to change notification settings - Fork 995
[Merged by Bors] - chore: rename the commandStart linter to whitespace
#33708
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
Conversation
The linter was always essentially checking all kinds of whitespace issues, so the name is equally descriptive already. A future PR will extend the linter to all proof bodies; then this name would have been actively misleading.
PR summary cb3ccde1edImport changes for modified filesNo significant changes to the import graph Import changes for all files
Declarations diff
You can run this locally as follows## summary with just the declaration names:
./scripts/declarations_diff.sh <optional_commit>
## more verbose report:
./scripts/declarations_diff.sh long <optional_commit>The doc-module for No changes to technical debt.You can run this locally as
note: file note: file |
Vierkantor
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM otherwise. I checked that all changes outside of the file defining this linter replace "commandstart" with "whitespace" (case insensitive).
|
bors d+ |
|
✌️ grunweg can now approve this pull request. To approve and merge a pull request, simply reply with |
Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
|
Thanks for the quick review! |
|
As this PR is labelled bors merge |
The linter was always essentially checking all kinds of whitespace issues, so the new name is equally descriptive already. A future PR will extend the linter to all proof bodies; then this name would have been actively misleading.
|
Canceled. |
|
bors merge |
The linter was always essentially checking all kinds of whitespace issues, so the new name is equally descriptive already. A future PR will extend the linter to all proof bodies; then this name would have been actively misleading.
|
Build failed: |
|
With the latest change, the test fails: deprecating the option only lints upon uses of it in code, but not inside |
|
Thanks! 🐙 Having the deprecation will help with the automatic removal later on and the bors d+ |
|
✌️ grunweg can now approve this pull request. To approve and merge a pull request, simply reply with |
|
Thanks for the fast review! |
The linter was always essentially checking all kinds of whitespace issues, so the new name is equally descriptive already. A future PR will extend the linter to all proof bodies; then this name would have been actively misleading.
|
Pull request successfully merged into master. Build succeeded: |
commandStart linter to whitespacecommandStart linter to whitespace
The linter was always essentially checking all kinds of whitespace issues,
so the new name is equally descriptive already.
A future PR will extend the linter to all proof bodies; then this name would
have been actively misleading.