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

doc: extend linters, manage deps via bazel #4503

Merged
merged 6 commits into from
Apr 19, 2024
Merged

Conversation

matzf
Copy link
Contributor

@matzf matzf commented Apr 8, 2024

  • use markdownlint-cli2 instead of ruby markdownlint

    Use Node.js-based github.com/DavidAnson/markdownlint-cli2, replacing the ruby-based github.com/markdownlint/markdownlint. This tool has a cleaner configuration file and that is well supported in vs code and other editors.

    Adapted from tools: add editor and lint configuration #4328.

  • add sphinx-lint, and manage the doc requirements via bazel/rules_python.

    Fix a large number of legitimage linter warnings; most cases were accidentally applying the "default role" (single backticks instead of double-backticks), or the occasional missing underscore after external links.

  • add bazel run targets to run sphinx-build and sphinx-autobuild via python deps managed by bazel. This makes it easy to locally build the documentation for devs that already have bazel set up (while hopefully keeping things still relatively straight-forward).

@matzf
Copy link
Contributor Author

matzf commented Apr 8, 2024

This change is Reviewable

Copy link
Contributor

@jiceatscion jiceatscion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me.

Reviewed 38 of 40 files at r1, 1 of 1 files at r2, 2 of 2 files at r3, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @matzf)

Copy link
Contributor

@oncilla oncilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 38 of 40 files at r1, 1 of 1 files at r2, 2 of 2 files at r3, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @matzf)

Copy link
Contributor

@oncilla oncilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @matzf)

matzf and others added 6 commits April 19, 2024 11:02
Use Node.js-based github.com/DavidAnson/markdownlint-cli2,
replacing the ruby-based github.com/markdownlint/markdownlint.
This tool has a cleaner configuration file and that is well
supported in vs code and other editors.

Adapted from scionproto#4328.

Co-authored-by: Dominik Roos <roos@anapaya.net>
of course that was totally on purpose, just testing...
@matzf matzf merged commit 5a5ceba into scionproto:master Apr 19, 2024
4 checks passed
@matzf matzf deleted the doc-lint branch April 19, 2024 09:16
This was referenced Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants