workflows: linter does not lint docstrings
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
Research direction
Inspect the repository's workflow, linter, and pre-commit configuration, then run the existing checks and cargo doc to reproduce the warning shown for cli/src/status.rs. Update the relevant configuration so documentation warnings such as unclosed HTML tags are checked automatically, and confirm the checks fail on the example issue.
Written by the indexing model from the issue text.
Description
The linters and pre-commit configs do not run the cargo doc and fail on docstring formatting issues like
warning: unclosed HTML tag `String`
--> cli/src/status.rs:43:10
|
43 | /// A Vec<String> where each element is an overlay name from the input ...
| ^^^^^^^^
|
- Dominant language
- Rust
- Stars
- 11
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from canonical/fpgad
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
bug enhancement workflows
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100