Closed tpansino closed 3 years ago
@RichardLitt, could you also start tagging releases after this is merged (assuming you agree to merge it 😅)? Pre-commit throws a warning unless you pin to a specific Git tag or SHA, and I see from the commit history that you're already versioning and bumping with each release.
Want to be a maintainer? I don't use this module at the moment.
Reopening as https://github.com/RichardLitt/standard-readme-cli/pull/6, because I didn't realize there was a CLI... :man_facepalming:
@RichardLitt, sure! Especially if that helps to get my changes merged :wink:.
Just so you know, I'm mostly a Python developer, and only have basic NodeJS skills, but I do work as a Senior DevOps engineer, so I'll pitch in where I can. :+1:
Hmm. Seems that I spoke too soon - I was tired. Thanks for being willing.
Pull Request
Description of Changes
README.md
files on-commit (via Git Hooks). Can also be used with this GitHub Action to enforce a passing check before merging. This also allows repo owners to define a single set of quality checks one time for both local development and the CI/CD pipeline.