chore: rename the Pages build job to build-site to avoid the required-status name#1170
Merged
Conversation
…ired-status name Rename jobs.build to jobs.build-site in pages.yml (updating deploy's `needs`) so no job named `build` remains anywhere: a job named `build` auto-creates a check-run named `build`, which collides with the required `build` commit status context (the collision #1156 fixed in pr-build.yml). Pages runs only on push-to-main / schedule, never on a PR, so its check-run cannot wedge a PR today; this is hygiene so a future PR trigger here could never reintroduce the collision. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019DP6TTvRPMYA6SPiA3Ff4u
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.
This PR renames the Pages workflow's
buildjob tobuild-site(updatingdeploy'sneeds) so no job namedbuildremains anywhere in the repo. A job namedbuildauto-creates a check-run namedbuild, which collides with the requiredbuildcommit status context, the same collision #1156 fixed inpr-build.yml. Pages runs only on push-to-main and the daily schedule, never on a PR, so its check-run cannot wedge a PR today; this is hygiene so a future PR trigger here could never reintroduce the collision.Note this touches
.github/so the scope check reports it out of scope and it needs a human merge; that is expected for a workflow change.🤖 Prepared with Claude Code