Using woke in Github for Conscious Language scans
summary
The project uses the tool woke to scan code, file names and content for non‑inclusive terms and to suggest alternatives. A GitHub Action runs woke on every PR across about 20 Linux System Roles repos. A needed change is implemented so warnings and errors are handled differently, and the official action is replaced by a custom GitHub action pointing to copied code. Some unavoidable terms (for example Microsoft “master” DB) are suppressed with ignored via config or per‑line comments.
AI-written summary · about
chapters (10)
- 0:00Conscious language intro
- 1:04Inclusive language matters
- 2:33Woke features and capabilities
- 3:37GitHub Actions + woke
- 4:22Woke implementation challenges
- 5:53Q&A: GitHub Actions & local use
- 7:39Tooling constraints with woke
- 8:42Ignoring terms in woke scans
- 9:51Inherited non-inclusive terms
- 11:17Closing remarks
related talks
07mLightning Talk: Checking Your Project for Non-inclusive Language
36mInclusive, Accessible Tech: Bias-Free Language In Code And Configurations
08mAutomated Checks Before Publishing Open Source, a Few Years La...
22mGetting Started with Open Source Project Insights
41mWords Matter
50mGitHub Features Every C++ Developer Should Know
01h 28mAutomating Developer Things with GitHub Action
08mA Simple, Yet Powerful Approach to Clean Code!