@@ -20,24 +20,11 @@ For now, see our opinions codified in [index.js](./index.js).
2020 touch .markdownlint.js
2121 ```
2222
23- 2. Install packages (during development ; will change after package is on the registry)
23+ 2. Install packages
2424
2525 - ` ` ` bash
26- npm i -D markdownlint-cli # if updating existing package, check for updates
27- ` ` `
28-
29- - Add package in the ` package.json` .
30-
31- ` ` ` json
32- {
33- " devDependencies" : {
34- " @github/markdownlint-github" : " github/markdownlint-github"
35- }
36- }
37- ` ` `
38-
39- - ` ` ` bash
40- npm install
26+ npm install -D markdownlint-cli # if updating existing package, check for updates
27+ npm install -D @github/markdownlint-github [--@github:registry=https://registry.npmjs.org]
4128 ` ` `
4229
43303. Add/modify your linting script in ` package.json` . Modify ` --ignore` and other arguments as needed.
@@ -126,13 +113,9 @@ We use `jest` tests as well, which should be an equally comfortable development
126113
127114To publish, merge your work to main (after PR process completed).
128115
129- For now, the repository is installed as a package whose location is the repository uploaded on GitHub. This will change .
116+ Manage version and publish on a new branch, and create a PR to merge these changes into main .
130117
131- # # Project status
132-
133- We' re currently in development on this. The delivery target date is August 15, 2022.
134-
135- [[Story] [Tooling] Tidy up, publish, and update markdown-lint package #1591](https://github.com/github/accessibility/issues/1591)
136- [[Epic] Increased Accessibility Linting Coverage #1397](https://github.com/github/accessibility/issues/1397)
137-
138- Effort initiated during a [markdown linting tooling spike](https://github.com/github/accessibility/issues/1429).
118+ ` ` ` bash
119+ npm version [major| minor| patch] # alternatively, manage version in package.json
120+ npm run publish
121+ ` ` `
0 commit comments