Skip to content

fix(weekly-agenda): don't tell owners their pre-drafted section is 'missing'#140

Open
BreadrichEngels wants to merge 1 commit into
mainfrom
fix/weekly-agenda-unconfirmed-section-copy
Open

fix(weekly-agenda): don't tell owners their pre-drafted section is 'missing'#140
BreadrichEngels wants to merge 1 commit into
mainfrom
fix/weekly-agenda-unconfirmed-section-copy

Conversation

@BreadrichEngels

Copy link
Copy Markdown
Contributor

Type of Change

  • Feature skill
  • Utility skill
  • Operational/container skill
  • Fix - bug fix or security fix to source code
  • Simplification
  • Documentation

Description

What: Fix the weekly-agenda flow's owner-nudge + escalation copy so it stops telling owners their agenda section is "missing" when it isn't.

Why: The weekly build always pre-drafts every owner's section from GitHub (their merged PRs / closed issues, or a "— space for 's update —" invite). But "responded" is tracked solely by the existence of inputs/<week>/<slug>.md, which is written only when the owner replies to confirm. So an owner who simply hadn't confirmed their already-populated section got escalated in #core-team-chat with "📝 I don't have 's agenda section for yet" — telling people their present entries were gone. It hit 7 owners for the 2026-07-01 cycle.

How: Reword escalationPost and askText to ask owners to review / confirm / correct their drafted section instead of implying it's empty. No change to detection or the nudge ladder — purely accurate copy. Added a regression test asserting the escalation never claims the section is missing (/I don't have/) and does ask for confirmation.

Tested: npx vitest run profiles/example/plugins/__tests__/weekly-agenda.test.mjs27 passed (incl. the new assertions).

cc @RonTuretzky — requesting your review; you own this flow.

…issing'

The nudge + escalation copy claimed "I don't have your agenda section yet"
and "time to fill in your section" — but the weekly build ALWAYS pre-drafts
every owner's section from GitHub. So owners who simply hadn't *confirmed*
their (already-populated) section were told, in-channel, that their entries
were missing.

Reword the ask + escalation to ask owners to review/confirm/correct their
drafted section instead of implying it's empty. Detection + nudge ladder
behaviour unchanged. Adds a regression test that the escalation never claims
the section is missing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant