Repository navigation
File an issue when the scheduled zone-shell audit fails - #1149
Merged
Merged
Conversation
The daily production audit previously failed silently in the Actions tab. Now a scheduled-run failure opens (or bumps) a tracking issue so a zone child that stops rendering the site shell gets noticed the same day. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1148. The daily scheduled
app-zone-shell-auditrun previously failed silently in the Actions tab; now a failure on a scheduled run opens a tracking issue (or comments on the existing one), so a zone child that stops rendering the site shell — or a route that goes down — gets noticed the same day. Each child repo also now guards its own shell in CI (scotland-income-tax-reform#12, uc-rebalancing#5, nics-exemption-inactive-employees#12, young-worker-nics#6, electricity-vat-cut#2, bus-fare-cap#10, student-loan-visualisation#5, cancelling-fuel-duty-rise#7, obbba-household-by-household#246), so this issue is the backstop, not the first line of defense.PR-run behavior is unchanged (
if: failure() && github.event_name == 'schedule'); the job gains an explicit minimal permissions block (contents: read,issues: write).🤖 Generated with Claude Code