-
Notifications
You must be signed in to change notification settings - Fork 94
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
Lint: Add a check for indentation being 4N spaces. #5772
Conversation
Make 'url' key optional in check specification. Document pyproject.toml fields.
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.
The multiple of four space check works well.
I spotted what looks like a duplicate code going through the CLi help:
U001:
"[scheduling][dependencies][<recurrence>]graph =" -> "[scheduling][graph]<recurrence> ="
U002:
"[scheduling][dependencies][<recurrence>]graph =" -> "[scheduling][graph]<recurrence> ="
@oliver-sanders U001 and U002 being the same is deliberate, but I agree, perhaps a little confusing. They are detecting two different patterns with the same underlying cause (The change from I have added a bracket with a little text to this effect to each message - hopefully that makes it OK for you? |
Pull request may be revisited after discussion with Tim and Oliver
…at_runtime * upstream/master: log_vc_info: handle long command output (cylc#5821) GH Actions: limit tutorial workflow to Py3.11 remove cylc task dependencies env var (cylc#5836) Refactor.lint (cylc#5718) protobuf 4.24.4 upgrade (cylc#5828) made reinstall work on multiple workflows Fix `IndepQueueManager` test (cylc#5832) Lint: Add a check for indentation being 4N spaces. (cylc#5772)
Make 'url' key optional in check specification.
Document pyproject.toml fields.
A couple of small fixes I found when looking at Cylc Lint for my talk on Thurs.
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).CHANGES.md
entry included if this is a change that can affect users?.?.x
branch.