galaxyproject / galaxyproject/planemo
Best Practice Guidelines - Lint Whitespace
Open
enhancement
linting
- Dominant language
- Python
- Stars
- 110
- Forks
- 102
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 13
Description
Lint white space acrodding to best practices here https://wiki.galaxyproject.org/Tools/BestPractices.
(4 lines per indent).
Contributor guide
Research direction
Start by reviewing the linked Galaxy Best Practices guidance and locating Planemo's existing whitespace or lint entry points. Apply the stated four-spaces-per-indent rule wherever the issue's lint scope covers it, then verify that the relevant lint checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100