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
Canonical cliff.toml should strip ZWSP at generation (bot regens re-import GitHub-defused mentions) #897
Squash-merge commit messages on the estate contain GitHub's ZWSP-defused
@-mentions (206 instances on maa-framework main). Every changelog-bot
regeneration via changelog-reusable.yml re-imports them into CHANGELOG.md,
which reddens any invisible-character linter on the consuming repo
(maa-framework #192 did exactly this, right after #188 had stripped them).
Stripping in the repo is whack-a-mole: the next bot run re-adds them.
Request
Add a commit_preprocessors rule (or equivalent post-processing) to the
canonical templates/cliff.toml that strips invisible characters (at least
U+200B; ideally the full set U+00A0 U+00AD U+2060 U+FEFF U+200B-U+200F
U+202A-U+202F U+2066-U+2069) from generated output, so all consuming repos stop
re-importing defused mentions at generation time.
Additional finding from the maa-framework rollout: the bot is currently self-feeding. Each merged bot PR adds a chore(changelog): regenerate... commit, which the next run dutifully changelogs into a new PR (#195 merge -> #196 containing only the #195 entry, ad infinitum). Request addition: canonical cliff.toml should also skip_commits the bot own message (e.g. ^chore\(changelog\)), so bot merges do not generate follow-up PRs. Until then the consuming repo closes bot PRs that contain only chore entries.
Activity
hyperpolymath commentedon Sep 22, 2026
Additional finding from the maa-framework rollout: the bot is currently self-feeding. Each merged bot PR adds a
chore(changelog): regenerate...commit, which the next run dutifully changelogs into a new PR (#195 merge -> #196 containing only the #195 entry, ad infinitum). Request addition: canonicalcliff.tomlshould alsoskip_commitsthe bot own message (e.g.^chore\(changelog\)), so bot merges do not generate follow-up PRs. Until then the consuming repo closes bot PRs that contain only chore entries.