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

GH Actions: update markdown lint workflow #158

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Apr 4, 2024

The author of the markdownlint-cli2 NPM package has published a GH Action runner for the package.

Advantages of switching to using that package:

  • No need to monitor which Node version is supported by the NPM package, nor to manually update that. This is especially useful as the markdownlint-cli2 doesn't use the GH release feature, which means that one can't subscribe to automatically get informed of releases (and the changelog of those).

Ref:

@jrfnl jrfnl added this to the 1.x Next milestone Apr 4, 2024
The author of the `markdownlint-cli2` NPM package has published a GH Action runner for the package.

Advantages of switching to using that package:
* No need to monitor which Node version is supported by the NPM package, nor to manually update that.
    This is especially useful as the `markdownlint-cli2` doesn't use the GH release feature, which means that one can't subscribe to automatically get informed of releases (and the changelog of those).

Ref:
* https://github.com/marketplace/actions/markdownlint-cli2-action
@jrfnl jrfnl force-pushed the feature/ghactions-update-markdownlint branch from 55f8647 to b056fc4 Compare April 4, 2024 02:57
@jrfnl jrfnl merged commit 3380dcc into 1.x Apr 4, 2024
84 checks passed
@jrfnl jrfnl deleted the feature/ghactions-update-markdownlint branch April 4, 2024 03:00
@coveralls
Copy link

coveralls commented Apr 4, 2024

Coverage Status

coverage: 96.232%. remained the same
when pulling b056fc4 on feature/ghactions-update-markdownlint
into 3ac4954 on 1.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants