Skip to content

Check markdown during CI #353

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Check markdown during CI #353

wants to merge 1 commit into from

Conversation

khssnv
Copy link
Member

@khssnv khssnv commented May 23, 2025

No description provided.

@khssnv khssnv force-pushed the khssnv/check-markdown branch from 509d389 to 59012a8 Compare May 23, 2025 10:52

Verified

This commit was signed with the committer’s verified signature.
khssnv Alisher A. Khassanov
@khssnv khssnv force-pushed the khssnv/check-markdown branch from 59012a8 to 88611df Compare May 23, 2025 10:58
@TriplEight
Copy link
Contributor

do we have a global process for linting? The least annoying (acceptance-test-wise) would be either shared list of plugins with settings, incl standardised lint rules, or pre-commit hooks.

@khssnv
Copy link
Member Author

khssnv commented Jun 10, 2025

do we have a global process for linting? The least annoying (acceptance-test-wise) would be either shared list of plugins with settings, incl standardised lint rules, or pre-commit hooks.

Not yet unfortunately, could you help to set it up, possibly with @akablockchain2?

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.

None yet

2 participants