Skip to content

Commit 8009344

Browse files
nschonninschonni
committed
fix: Enable remark-lint-unordered-list-marker-style
Upstream style uses asterisks
1 parent 14a533d commit 8009344

43 files changed

Lines changed: 509 additions & 510 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.remarkrc‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@
33
"remark-frontmatter",
44
"remark-preset-lint-node",
55
["remark-lint-first-heading-level", false],
6-
["remark-lint-maximum-line-length", false],
7-
["remark-lint-unordered-list-marker-style", false]
6+
["remark-lint-maximum-line-length", false]
87
]
98
}

‎CONTRIBUTING.md‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -12,62 +12,62 @@ This project follows the [Conventional Commits][] specification.
1212

1313
There is a built-in commit linter. Basic rules:
1414

15-
- Commit messages must be prefixed with the name of the changed subsystem, followed by a colon and a space and start with an imperative verb. Check the output of `git log --oneline files/you/changed` to find out what subsystems your changes touch.
15+
* Commit messages must be prefixed with the name of the changed subsystem, followed by a colon and a space and start with an imperative verb. Check the output of `git log --oneline files/you/changed` to find out what subsystems your changes touch.
1616

1717
Supported subsystems:
1818

1919
> build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test
2020
21-
- Commit messages **must** start with a capital letter
22-
- Commit messages **must not** end with a period `.`
21+
* Commit messages **must** start with a capital letter
22+
* Commit messages **must not** end with a period `.`
2323

2424
## Collaboration Policy
2525

26-
- All changes must come in a PR
27-
- All changes must be reviewed by a member of @nodejs/nodejs.dev,
26+
* All changes must come in a PR
27+
* All changes must be reviewed by a member of @nodejs/nodejs.dev,
2828
@nodejs/website, or @nodejs/website-redesign
29-
- Pull Requests must be open for at least 48 hours unless included in the special exemptions section below
29+
* Pull Requests must be open for at least 48 hours unless included in the special exemptions section below
3030

3131
### Special Exemptions
3232

3333
Pull requests seeking to make any of the following changes do not need to wait 24 hours
3434

35-
- Errata fixes
36-
- Infrastructure Maintenance
37-
- Tests
35+
* Errata fixes
36+
* Infrastructure Maintenance
37+
* Tests
3838

3939
## Landing Pull Requests
4040

4141
### Before you can land
4242

43-
- The Status Checks for the test suite must pass
44-
- There must be at least one sign off
45-
- There must be no objections after a 48 hour period
43+
* The Status Checks for the test suite must pass
44+
* There must be at least one sign off
45+
* There must be no objections after a 48 hour period
4646

4747
The default for each contribution is that it is accepted once no collaborator has an objection. During review collaborators may also request that a specific contributor who is most versed in a particular area gives a "LGTM" before the PR can be merged.
4848

4949
In the case of an objection being raised in a pull request by another collaborator, all involved collaborators should seek to arrive at a consensus by way of addressing concerns being expressed by discussion, compromise on the proposed change, or withdrawal of the proposed change.
5050

5151
## When Landing
5252

53-
- Do not use merge button
54-
- [`squash`][] pull-requests made up of multiple commits
55-
- Land how you like as long as there are no merge commits
53+
* Do not use merge button
54+
* [`squash`][] pull-requests made up of multiple commits
55+
* Land how you like as long as there are no merge commits
5656

5757
## Developer's Certificate of Origin 1.1
5858

5959
By making a contribution to this project, I certify that:
6060

61-
- (a) The contribution was created in whole or in part by me and I have the right to
61+
* (a) The contribution was created in whole or in part by me and I have the right to
6262
submit it under the open source license indicated in the file; or
63-
- (b) The contribution is based upon previous work that, to the best of my knowledge,
63+
* (b) The contribution is based upon previous work that, to the best of my knowledge,
6464
is covered under an appropriate open source license and I have the right under that
6565
license to submit that work with modifications, whether created in whole or in part
6666
by me, under the same open source license (unless I am permitted to submit under a
6767
different license), as indicated in the file; or
68-
- (c) The contribution was provided directly to me by some other person who certified
68+
* (c) The contribution was provided directly to me by some other person who certified
6969
(a), (b) or (c) and I have not modified it.
70-
- (d) I understand and agree that this project and the contribution are public and that
70+
* (d) I understand and agree that this project and the contribution are public and that
7171
a record of the contribution (including all personal information I submit with it,
7272
including my sign-off) is maintained indefinitely and may be redistributed consistent
7373
with this project or the open source license(s) involved.

‎OKR.md‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,34 +6,34 @@ The Nodejs.dev project uses Objectives and Key Results to provide direction and
66

77
OKRs consist of two elements:
88

9-
- Objectives
10-
- Objectives are qualitative, ambitious, and memorable definitions of the things we as a committee would like to achieve.
11-
- Key Results
12-
- Key Results are a set of metrics by which we can measure progress toward their objectives. Like objectives, they should be ambitious and overestimate what we can accomplish.
9+
* Objectives
10+
* Objectives are qualitative, ambitious, and memorable definitions of the things we as a committee would like to achieve.
11+
* Key Results
12+
* Key Results are a set of metrics by which we can measure progress toward their objectives. Like objectives, they should be ambitious and overestimate what we can accomplish.
1313

1414
### External References
1515

1616
Here are some external references that may help provide further context on OKRs.
1717

18-
- [Guide: Set goals with OKRs](https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/)
19-
- [What is OKR?](https://felipecastro.com/en/okr/what-is-okr/)
20-
- [What Are OKRs? How to Use OKRs for Planning (and Achieving) Your Goals](https://plan.io/blog/what-are-okrs/)
18+
* [Guide: Set goals with OKRs](https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/)
19+
* [What is OKR?](https://felipecastro.com/en/okr/what-is-okr/)
20+
* [What Are OKRs? How to Use OKRs for Planning (and Achieving) Your Goals](https://plan.io/blog/what-are-okrs/)
2121

2222
## OKRs (2020 Set 1):
2323

24-
- **Objective:** Continuity of process
24+
* **Objective:** Continuity of process
2525

26-
- **Key Result:** Staging and CI have each have a published technical administration summary and a how-to guide.
27-
- **Key Result:** Consider using issue templates to facilitate operations.
26+
* **Key Result:** Staging and CI have each have a published technical administration summary and a how-to guide.
27+
* **Key Result:** Consider using issue templates to facilitate operations.
2828

29-
- **Objective:** Identify areas of progress and future goals
29+
* **Objective:** Identify areas of progress and future goals
3030

31-
- **Key Result:** Create a feature roadmap
32-
- **Key Result:** Track features & priorities in one place (project?)
33-
- **Key Result:** Make available the top two features in nodejs.org:
31+
* **Key Result:** Create a feature roadmap
32+
* **Key Result:** Track features & priorities in one place (project?)
33+
* **Key Result:** Make available the top two features in nodejs.org:
3434
1. Docs — https://nodejs.org/en/docs/
3535
2. Download — https://nodejs.org/en/download/
3636

37-
- **Objective:** Make explicit the channels of interfacing internally and with larger org
38-
- **Key Result:** Write down implicit team norms
39-
- **Key Result:** How do we propose and review non-feature changes in PRs?
37+
* **Objective:** Make explicit the channels of interfacing internally and with larger org
38+
* **Key Result:** Write down implicit team norms
39+
* **Key Result:** How do we propose and review non-feature changes in PRs?

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,9 +117,9 @@ The `src/documentation` directory currently contains all the getting started con
117117

118118
Looking for more guidance? Full documentation for Gatsby lives [on the website](https://next.gatsbyjs.org/). Here are some places to start:
119119

120-
- **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://next.gatsbyjs.org/tutorial/).** It starts with zero assumptions about your level of ability and walks through every step of the process.
120+
* **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://next.gatsbyjs.org/tutorial/).** It starts with zero assumptions about your level of ability and walks through every step of the process.
121121

122-
- **To dive straight into code samples head [to our documentation](https://next.gatsbyjs.org/docs/).** In particular, check out the "Guides", API reference, and "Advanced Tutorials" sections in the sidebar.
122+
* **To dive straight into code samples head [to our documentation](https://next.gatsbyjs.org/docs/).** In particular, check out the "Guides", API reference, and "Advanced Tutorials" sections in the sidebar.
123123

124124
## 🏛 Governance
125125

0 commit comments

Comments
 (0)