You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, we have a project to eliminate non-inclusive language from Linux-system-roles.
Running a utility woke (now it's supported in tox. please install the latest tox-lsr and run tox -e woke), two non-inclusive words are reported - sanity and master.
The word sanity is easily eliminated, but master is not since it's tightly coupled with the SQL context, e.g., as master key.
There are two ways to skip the check - adding wokeignore:rule=master to each master appearing in the source code, or skipping them as warning by applying get-woke/woke#252. Which way should we go or could there be some other ideas to workaround master?
The text was updated successfully, but these errors were encountered:
There are too many uses of master in the code. Running woke with --count-only-error-for-failure results in a success, so it's only the word master that matters. And the role cannot fix master in the SQL Server context. The role can only fix the use of master in unrelated context, e.g. rename the GitHub branch master > main.
Hello, we have a project to eliminate non-inclusive language from Linux-system-roles.
Running a utility
woke
(now it's supported in tox. please install the latest tox-lsr and run tox -e woke), two non-inclusive words are reported -sanity
andmaster
.The word
sanity
is easily eliminated, butmaster
is not since it's tightly coupled with the SQL context, e.g., asmaster key
.There are two ways to skip the check - adding
wokeignore:rule=master
to eachmaster
appearing in the source code, or skipping them aswarning
by applying get-woke/woke#252. Which way should we go or could there be some other ideas to workaroundmaster
?The text was updated successfully, but these errors were encountered: