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
{{ message }}
Repository navigation
[text-auditor] Fix three concrete user-facing text defects (stale workflow name, typo, and misleading log extractor wording) #749
-o .github/workflows/trigger-code-complexity-detector.yml && \ Why:gh-agent-workflows/code-simplifier/ is no longer present, while gh-agent-workflows/code-complexity-detector/ exists. The current install command is misleading and likely broken.
2. Typo in maintainer-facing workflow prompt text
File:.github/workflows/gh-aw-mention-in-issue.md (line 141) Current text:Unless instructred otherwise, if you do create an issue or a pull request, assign it to the user who requested the change that resulted in the creation of the issue or pull request. Suggested fix:Unless instructed otherwise, if you do create an issue or a pull request, assign it to the user who requested the change that resulted in the creation of the issue or pull request. Why: Clear spelling error in user-facing instruction text.
3. Log-extractor help text says it extracts only errors, but it also matches warnings
File:scripts/extract-log-errors.py (lines 3 and 101; behavior evidence at line 33) Current text:
Module docstring: Extract errors and failures from GitHub Actions log files.
Extract warnings, errors, and failures from GitHub Actions log files. Why:DEFAULT_PATTERNS includes r"##\[warning\]" (line 33), so current user-facing wording is misleading relative to behavior.
Completeness Pass (verified occurrences)
instructred -> 1 user-facing source occurrence in .github/workflows/gh-aw-mention-in-issue.md.
code-simplifier/example.yml and trigger-code-simplifier.yml -> 2 occurrences, both in docs/index.md lines 112-113.
Extract errors and failures from GitHub Actions log files. -> 1 occurrence (scripts/extract-log-errors.py:3).
Activity
github-actions commentedon Mar 26, 2026
This issue was automatically closed because it expired on 2026-03-26T13:42:09.810Z.