72d92413a2
* spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
25 lines
616 B
YAML
25 lines
616 B
YAML
name: Spell checking
|
|
on:
|
|
pull_request_target:
|
|
push:
|
|
|
|
jobs:
|
|
build:
|
|
name: Spell checking
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: checkout-merge
|
|
if: "contains(github.event_name, 'pull_request')"
|
|
uses: actions/checkout@v2.0.0
|
|
with:
|
|
ref: refs/pull/${{github.event.pull_request.number}}/merge
|
|
fetch-depth: 5
|
|
- name: checkout
|
|
if: "!contains(github.event_name, 'pull_request')"
|
|
uses: actions/checkout@v2.0.0
|
|
with:
|
|
fetch-depth: 5
|
|
- uses: check-spelling/check-spelling@0.0.17-alpha
|
|
with:
|
|
config: .github/actions/spell-check
|