Skip to content

Commit c446d85

Browse files
committed
Also check files in /docs. Fix errors in those files.
Also add Base Vocabulary so that the Learning Path can add custom exceptions when using spell checking.
1 parent fffdb92 commit c446d85

5 files changed

Lines changed: 7 additions & 4 deletions

File tree

.github/workflows/vale.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ jobs:
2020
- name: Vale Linting
2121
uses: errata-ai/vale-action@reviewdog
2222
with:
23-
files: '["introduction/", "trusted-committer/", "contributor/", "product-owner/", "project-leader/"]'
23+
files: '["docs/","introduction/", "trusted-committer/", "contributor/", "product-owner/", "project-leader/"]'
2424
vale_flags: '--glob=!*/*/*'
2525
filter_mode: added # one of: added, diff_context, file, nofilter
2626
debug: true

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,4 @@ scripts/newsite
66
scripts/.env
77
.vs
88
.github/vale/*
9+
!.github/vale/Vocab/Base

.vale.ini

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,5 +3,7 @@ MinAlertLevel = suggestion
33

44
Packages = https://github.com/InnerSourceCommons/isc-styles/releases/latest/download/ISC.zip
55

6+
Vocab = Base
7+
68
[*]
79
BasedOnStyles = ISC

docs/adding-trusted-committers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
This document describes how to add a new Trusted Committer to the InnerSource Learning Path.
22

3-
1. Share your suggestion for new Trusted Commiter in the [:lock:learning-path-trusted-committers][learning-path-trusted-committers] private _Slack_ channel.
4-
2. If you have some agreeement (or even [lazy consensus](https://community.apache.org/committers/lazyConsensus.html)), then move forward.
3+
1. Share your suggestion for new Trusted Committer in the [:lock:learning-path-trusted-committers][learning-path-trusted-committers] private _Slack_ channel.
4+
2. If you have some agreement (or even [lazy consensus](https://community.apache.org/committers/lazyConsensus.html)), then move forward.
55
3. Create a pull request to the [Trusted Committers] section of the README with the new person.
66
4. Invite the person into the [:lock:learning-path-trusted-committers][learning-path-trusted-committers] _Slack_ channel.
77
5. Add the person to the [@InnerSourceCommons/learning-path] _GitHub_ team.

docs/spell-and-style-checking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Any issues found will be shown in the terminal and would look like this:
3737
'consollidating'?
3838
```
3939

40-
## How to check new Learnign Path content coming in via Pull Requests
40+
## How to check new Learning Path content coming in via Pull Requests
4141

4242
This happens automatically, using GitHub Actions and this workflow [vale.yml](.github/workflows/vale.yml).
4343

0 commit comments

Comments
 (0)