-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can we provide a custom spell list and ignore list? #62
Comments
@kalenmike yes, I've been thinking the same thing. As the actions grow there are a few options here, but they each have their drawbacks: Single Repo - Single Branch (current approach, comingling arguments)jobs:
ultralytics-actions:
runs-on: ubuntu-latest
steps:
- name: Run Ultralytics Formatting
uses: ultralytics/actions@main
with:
token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, do not modify
actions-arg1:
actions-arg2:
... Single Repo - Multi Branch (non-conventional, more complicated to maintain)Here a single repo supports multiple branches that are named for their step, i.e. jobs:
ultralytics-actions:
runs-on: ubuntu-latest
steps:
- name: Run Ultralytics Formatting
uses: ultralytics/actions@format
with:
token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, do not modify
format-arg1:
format-arg2:
...
- name: Run Ultralytics Summary
uses: ultralytics/actions@summary
with:
token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, do not modify
summary-arg1:
summary-arg2:
... Multi Repo (higher maintenance, duplication of effort, etc.)Here a single repo supports a single step in it's Main advantage is capability to publish multiple actions to the Marketplace. jobs:
ultralytics-actions:
runs-on: ubuntu-latest
steps:
- name: Run Ultralytics Formatting
uses: ultralytics/actions-format@main
with:
token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, do not modify
format-arg1:
format-arg2:
...
- name: Run Ultralytics Summary
uses: ultralytics/actions-summary@main
with:
token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, do not modify
summary-arg1:
summary-arg2:
... |
@kalenmike another faster option is just to update the default spellchecker ignore lists here: Lines 121 to 127 in 6e36e15
|
We don't want to run spellcheck on package file names, can we ignore package and requirement files? Also can we provide a custom word list to ignore exceptions for strange spellings?
The text was updated successfully, but these errors were encountered: