Skip to content

ci: one email a day: a daily digest, and no other workflow mentions or assigns - #659

Merged
Nawid3333 merged 2 commits into
mainfrom
ci/daily-digest
Nov 9, 2026
Merged

Nawid3333 merged 2 commits into
mainfrom
ci/daily-digest

Conversation

@Nawid3333

Copy link
Copy Markdown
Owner

You asked for one email per day instead of one for every event. GitHub emails every @mention and every assignment, so:

No workflow mentions or assigns you any more

  • 16 workflows write their issues, PRs and comments without @owner and without --assignee. Their meaning is unchanged; the reworded PR texts now point to the digest.
  • tests/workflows/no-mentions.test.sh fails if any workflow but the digest mentions or assigns again.

daily-digest.yml: the one email

  • Runs daily at 10:00 UTC, after the 07:00 update runs and their verdicts. It comments once on a pinned issue, Daily digest, and @mentions you once.
  • Window: from the last digest's marker to 10 minutes before the run, at most 7 days back. Nothing is lost between runs, a closed digest issue doesn't reset the window, and the newest 10 minutes go into the next digest because search may not have indexed them yet.
  • Content:
    • failed runs that ended in the window, grouped by workflow and branch, each with how it stands now (passed since, failure or running);
    • the open PRs with update-prs.yml's verdict, marked new or "verdict changed";
    • PRs merged or closed, issues opened or closed, releases;
    • comments from anyone else, including review comments;
    • open and new Dependabot and code scanning alerts.
  • A quiet day posts nothing. If the digest run itself fails, its failure step @mentions you.

Your part (GitHub settings; docs/maintenance.md, "Email: one a day")

  1. Settings > Notifications > System > Actions: untick Email (keep Web).
  2. Settings > Notifications > Dependabot alerts: untick Email, or choose the weekly digest.
  3. Unsubscribe from older PRs and issues you were mentioned on; otherwise they keep emailing on every comment until they close.

Checks

  • Local: lint, typecheck, vitest (3484), every workflow test (daily-digest.test.sh 50 checks; no-mentions.test.sh was also run against the old main, where it fails on the old mentions), actionlint, zizmor.
  • Codex reviewed the digest script: 8 findings, all fixed with tests.
  • GLM reviewed the de-mention diff in two parts: no findings. A second GLM review of the digest: 3 of 4 findings real and fixed.
  • The GLM agent drafted the doc rewording; I checked and finished it.

🤖 Generated with Claude Code

Nawid3333 and others added 2 commits November 9, 2026 19:17
…r assigns

The owner's wish (2026-11-09): "just one email per repo that gets sent daily, which
summarizes all the stuff". GitHub emails an @mention and an assignment, so:

- No workflow @mentions or assigns the owner any more (16 workflows, their comments and
  issues written plainly); tests/workflows/no-mentions.test.sh fails if one does again.
- daily-digest.yml, daily at 10:00 UTC, comments once on the pinned issue "Daily digest",
  @mentioning the owner once: failed runs that ended in the window (by workflow id and
  branch, with how each stands now), the open PRs with update-prs.yml's verdict, PRs merged
  or closed, issues opened or closed, releases, comments from others (review comments too),
  open and new security alerts. The window runs from the last digest's marker to ten
  minutes before the run; a quiet day posts nothing. Its own failure @mentions the owner.
- docs/maintenance.md, "Email: one a day": the GitHub settings that send the rest.

Reviewed by Codex (8 findings, all taken) and GLM (unmention diff: none; digest: 3 of 4).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Nawid3333
Nawid3333 merged commit 7ff35e0 into main Nov 9, 2026
39 checks passed
@Nawid3333
Nawid3333 deleted the ci/daily-digest branch November 9, 2026 19:52
@github-actions github-actions Bot mentioned this pull request Nov 10, 2026
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.

1 participant