Draft
fix(google-indexing): treat 403 PERMISSION_DENIED as warning, not failure#21
Conversation
…failure Co-authored-by: samtrion <3283596+samtrion@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
samtrion
August 9, 2026 19:54
View session
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.
The Google Indexing workflow was hard-failing CI on every
page_buildevent because the service account lacks verified ownership ofdaily-devops.netin Search Console, causing the API to return HTTP 403. Since this is a configuration gap (not a transient or code error), exiting with code 1 is wrong.Changes
warnedbucket for 403 responses —PERMISSION_DENIEDerrors are logged asWARNand tracked separately; only non-403 failures (5xx, 429, etc.) triggersys.exit(1)[!]warnings instead of[ ]failures, making the distinction visible in the job summary