devto-github-template
markdownlint-cli
devto-github-template | markdownlint-cli | |
---|---|---|
1 | 3 | |
11 | 787 | |
- | - | |
10.0 | 8.1 | |
about 2 years ago | 6 days ago | |
JavaScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
devto-github-template
-
My setup for publishing to Dev.to using github
Once this is done, I'm ready to start editing the markdown. By default, Dev.to articles require certain headers for them to be picked up, so this file has been started with the following:
markdownlint-cli
-
My setup for publishing to Dev.to using github
repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v2.3.0 hooks: - id: check-yaml - id: end-of-file-fixer - id: trailing-whitespace - repo: https://github.com/Yelp/detect-secrets rev: v1.4.0 hooks: - id: detect-secrets - repo: https://github.com/igorshubovych/markdownlint-cli rev: v0.33.0 hooks: - id: markdownlint args: ["--disable=MD013"] # this removes line length warnings
-
Recommend Visual Studio Code extensions along with your code
We saw how we can utilize extensions.json to recommend VS Code extensions with code to developers. But why do we want to do this? The purpose is making life of developers/contributors easier. For example, I use indent-rainbow to make indents more readable. Let's say that you are using markdownlint-cli with your CI setup then you may consider adding markdownlint to extensions.json. This extension runs same rules with markdownlint-cli and immediately detects linting errors while you typing. This allows contributors to detect linting errors before pushing anything and waiting CI pipeline (linting) to fail. This shortens the loop significantly. So if you (as a repository/codebase maintainer) think that a particular VS Code extension helps contributors then add it. But don't recommend anything satisfying your personal choices like color theme, icon set, etc. They won't help other developers much.
-
TIL: Use pre-commit hook - the framework
$ cd til $ pre-commit autoupdate Updating https://github.com/pre-commit/pre-commit-hooks ... [INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks. updating v2.3.0 -> v4.0.1. Updating https://github.com/igorshubovych/markdownlint-cli ... already up to date.
What are some alternatives?
DevToArticleRepo - connects a github repo to the markdown repo
prettier - Prettier is an opinionated code formatter.
markdown-here - Google Chrome, Firefox, and Thunderbird extension that lets you write email in Markdown and render it before sending.
pre-commit-hooks - git pre-commit hooks that work with http://pre-commit.com/
detect-secrets - An enterprise friendly way of detecting and preventing secrets in code.
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
pre-commit-hooks - Some out-of-the-box hooks for pre-commit
check-jsonschema - A CLI and set of pre-commit hooks for jsonschema validation with built-in support for GitHub Workflows, Renovate, Azure Pipelines, and more!
pre-commit-hooks - An experiment with Git pre-commit hooks
blog - https://blog.alperyazar.com
pre-commit-perl - perl hooks for https://pre-commit.com/