isocpp / isocpp/CppCoreGuidelines
Update remark to find more already configured warnings.
Open
@AndrewPardoe is already working on this.
Since Feb 13, 2017.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
Updating to a newer version of remark can be seen here:
https://github.com/jacobl-at-ms/CppCoreGuidelines/commit/91bad7bae40ee7f19ec154e1420370952ee955c4
When updating to a newer version of remark, these new warnings are found:
94:1-94:36 warning Don’t use multiple top level headings (94:1) no-multiple-toplevel-headings remark-lint
133:1-133:48 warning Don’t use multiple top level headings (133:1) no-multiple-toplevel-headings remark-lint
346:1-346:43 warning Don’t use multiple top level headings (346:1) no-multiple-toplevel-headings remark-lint
1024:1-1024:43 warning Don’t use multiple top level headings (1024:1) no-multiple-toplevel-headings remark-lint
1953:1-1953:41 warning Don’t use multiple top level headings (1953:1) no-multiple-toplevel-headings remark-lint
3502:1-3502:57 warning Don’t use multiple top level headings (3502:1) no-multiple-toplevel-headings remark-lint
7604:1-7604:42 warning Don’t use multiple top level headings (7604:1) no-multiple-toplevel-headings remark-lint
7857:1-7857:50 warning Don’t use multiple top level headings (7857:1) no-multiple-toplevel-headings remark-lint
8729:1-8729:54 warning Don’t use multiple top level headings (8729:1) no-multiple-toplevel-headings remark-lint
11153:1-11153:47 warning Don’t use multiple top level headings (11153:1) no-multiple-toplevel-headings remark-lint
11521:1-11521:62 warning Don’t use multiple top level headings (11521:1) no-multiple-toplevel-headings remark-lint
12848:1-12848:43 warning Don’t use multiple top level headings (12848:1) no-multiple-toplevel-headings remark-lint
13760:1-13760:56 warning Don’t use multiple top level headings (13760:1) no-multiple-toplevel-headings remark-lint
13923:1-13923:65 warning Don’t use multiple top level headings (13923:1) no-multiple-toplevel-headings remark-lint
16048:1-16048:47 warning Don’t use multiple top level headings (16048:1) no-multiple-toplevel-headings remark-lint
16140:1-16140:42 warning Don’t use multiple top level headings (16140:1) no-multiple-toplevel-headings remark-lint
16483:1-16483:50 warning Don’t use multiple top level headings (16483:1) no-multiple-toplevel-headings remark-lint
16652:1-16652:43 warning Don’t use multiple top level headings (16652:1) no-multiple-toplevel-headings remark-lint
16700:1-16700:46 warning Don’t use multiple top level headings (16700:1) no-multiple-toplevel-headings remark-lint
16961:1-16961:44 warning Don’t use multiple top level headings (16961:1) no-multiple-toplevel-headings remark-lint
17108:1-17108:40 warning Don’t use multiple top level headings (17108:1) no-multiple-toplevel-headings remark-lint
17680:1-17680:53 warning Don’t use multiple top level headings (17680:1) no-multiple-toplevel-headings remark-lint
17824:1-17824:53 warning Don’t use multiple top level headings (17824:1) no-multiple-toplevel-headings remark-lint
18371:1-18371:65 warning Don’t use multiple top level headings (18371:1) no-multiple-toplevel-headings remark-lint
18468:1-18468:50 warning Don’t use multiple top level headings (18468:1) no-multiple-toplevel-headings remark-lint
18474:1-18474:59 warning Don’t use multiple top level headings (18474:1) no-multiple-toplevel-headings remark-lint
18519:1-18519:52 warning Don’t use multiple top level headings (18519:1) no-multiple-toplevel-headings remark-lint
19073:1-19073:36 warning Don’t use multiple top level headings (19073:1) no-multiple-toplevel-headings remark-lint
19211:1-19211:63 warning Don’t use multiple top level headings (19211:1) no-multiple-toplevel-headings remark-lint
19269:1-19269:15 warning Don’t use multiple top level headings (19269:1) no-multiple-toplevel-headings remark-lint
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.