Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Based on the MIR team discussion and PR feedback clarify that this needs to be run in source and even more on built binaries. Further clarify how to look for setuid and setgid. And finally, those are not rules or content to leave in the final post, so these hints are now prefixed with RULE as we usually do for this kind of content. Signed-off-by: Christian Ehrhardt <[email protected]>
- Loading branch information
d39c10d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@check-spelling-bot Report
🔴 Please review
See the 📜action log for details.
Unrecognized words (2)
Hrn
setgid
To accept ✔️ these unrecognized words as correct, run the following commands
... in a clone of the [email protected]:cpaelzer/ubuntu-mir.git repository
on the
add-commands
branch (ℹ️ how do I use this?):Available 📚 dictionaries could cover words not in the 📘 dictionary
This includes both expected items (10) from .github/actions/spelling/expect.txt and unrecognized words (2)
Consider adding them using (in
.github/workflows/spelling.yml
):To stop checking additional dictionaries, add:
✏️ Contributor please read this
By default the suggested command will add the listed items to the.github/actions/spelling/expect.txt
. This is not always desired!If a listed items is
.github/actions/spelling/allow
..github/actions/spelling/expect.txt
.See the
README.md
in each directory for more information.🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push – it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉