Skip to content
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

Add check for non-inclusive language #310

Merged
merged 2 commits into from
Dec 16, 2022

Conversation

nhosoi
Copy link
Contributor

@nhosoi nhosoi commented Dec 15, 2022

Add a check for usage of terms and language that is considered
non-inclusive. We are using the woke tool for this with a wordlist
that can be found at
https://github.com/linux-system-roles/tox-lsr/blob/main/src/tox_lsr/config_files/woke.yml

CHANGELOG.md - cleanup non-inclusive words.

CHANGELOG.md Outdated

- Use GITHUB_REF_NAME as name of push branch; fix error in branch detection [citest skip]

We need to get the name of the branch to which CHANGELOG.md was pushed.
For now, it looks as though `GITHUB_REF_NAME` is that name. But don't
trust it - first, check that it is `main` or `master`. If not, then use
trust it - first, check that it is `main` or `master`. If not, then use // wokeignore:rule=master
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok - but I'd like to see what @Jakuje says about linux-system-roles/crypto_policies#54 (comment) - if the right answer is "just edit CHANGELOG.md to remove the problematic terms rather than put wokeignore in CHANGELOG.md" then this PR becomes much smaller and simpler i.e. can use the official woke instead of the custom

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, but this changelog item specifically refers to the master branch... How we could describe it without using the word master... In this case, I can just remove it, as it does not look that important(?), but there could be some cases that do not allow it???

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, but this changelog item specifically refers to the master branch... How we could describe it without using the word master... In this case, I can just remove it, as it does not look that important(?), but there could be some cases that do not allow it???

I think we can remove these entire entries from the changelog.

The problem with the auto-changelog generation that I wrote is

  • it is pretty stupid - it just collects all of the git commit messages
  • it requires a non-lazy human to edit - I should really have just summarized all of these changes as something like "fix github publish action" or something like that

Especially in this case - these can be replaced with - fix github action for publishing roles or similar

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same below - just say - github action ansible test improvements

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @richm! I'm updating CHANGELOG as you suggested.

@nhosoi
Copy link
Contributor Author

nhosoi commented Dec 15, 2022

Test was successful. Warning is not counted as an error.

Prepare all required actions
Run ./.github/actions/custom-woke-action
Run $GITHUB_ACTION_PATH/entrypoint.sh
 Installing woke ... https://github.com/nhosoi/woke
 Running woke ...
  Warning: `sanity` may be insensitive, use `confidence`, `quick check`, `coherence check` instead
  No findings found.

@richm
Copy link
Collaborator

richm commented Dec 15, 2022

please remove/change the reference at https://github.com/linux-system-roles/logging/pull/310/files#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edL448 also - then you can just use the standard woke action and don't have to use the custom action

@nhosoi nhosoi changed the title [WIP] Add check for non-inclusive language Add check for non-inclusive language Dec 15, 2022
@nhosoi
Copy link
Contributor Author

nhosoi commented Dec 15, 2022

[citest]

Add a check for usage of terms and language that is considered
non-inclusive. We are using the woke tool for this with a wordlist
that can be found at
https://github.com/linux-system-roles/tox-lsr/blob/main/src/tox_lsr/config_files/woke.yml

Signed-off-by: Noriko Hosoi <[email protected]>
@nhosoi nhosoi merged commit 1c4d3bb into linux-system-roles:main Dec 16, 2022
@nhosoi
Copy link
Contributor Author

nhosoi commented Dec 16, 2022

Thank you for your review, @richm. Merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants