Skip to content

chore(landing): re-land alert-triage fixes via PR (bbc6dbe, b29e208, 9862b71) - #94

Merged
alexeygrigorev merged 6 commits into
mainfrom
fix/alert-triage-reland
Nov 20, 2026
Merged

alexeygrigorev merged 6 commits into
mainfrom
fix/alert-triage-reland

Conversation

@alexeygrigorev

Copy link
Copy Markdown
Member

Process re-land: alert-triage fixes through a PR

The three 20 Nov alert-triage fixes were pushed directly to main, which
violates this task's landing rule ("PR, CI green on exact head, merge").
The substance was already accepted (CI+deploy run 44824917237 green on the
exact head 9862b71); this PR repairs the landing path without changing
any content.

  • First three commits revert bbc6dbe, b29e208 and 9862b71.
  • Last three re-apply them, so the tree of this branch is byte-identical
    to main at 9862b71
    (git diff origin/main HEAD is empty).
  • Merging produces the merge commit the merge gate records; the push-run
    deploy afterwards re-applies the identical template (no-op).

Nothing new is introduced; the preserved cli-help-discoverability branch
is unrelated work from another task and is deliberately not bundled here.

Fixes carried (already live, re-landed for process compliance):

  • bbc6dbe fix(notify): keep personal inboxes off operator mail by default
  • b29e208 ci(alarms): print the telegram webhook-health alarm state and history
  • 9862b71 fix(queue): redrive non-policy failures in 15 minutes, not 30

@alexeygrigorev
alexeygrigorev merged commit bbd4fa5 into main Nov 20, 2026
14 checks passed
@alexeygrigorev
alexeygrigorev deleted the fix/alert-triage-reland branch November 20, 2026 22:37
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