docs-deploy: Skip pipeline on default-branch pushes without docs changes#99
Merged
Conversation
Pass effective_any_modified from docs-build's check job to docs-deploy via artifact. On push events, docs-deploy reads the artifact instead of hardcoding has-changes=true, so the build/deploy/link-index pipeline is skipped when no docs-relevant files changed. Version branches keep current behavior (always run) via the existing use-release-branches override in docs-build. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The override previously forced effective_any_modified=true on every push to a version branch. Now it only triggers when github.event.created is true (first push), so subsequent pushes to version branches respect actual docs-change detection like the default branch. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Mpdreamz
approved these changes
May 12, 2026
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
2 participants
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.
What
Skip the docs-deploy pipeline (build, deploy, link-index update) on pushes to the default branch when no docs-relevant files changed.
Why
Currently
docs-deploy.ymlhardcodeshas-changes: 'true'for all push events, triggering the full pipeline on every push to main — even when only code or config files changed.How
Pass
effective_any_modifiedfromdocs-build'scheckjob todocs-deployvia a lightweight artifact. On push events,docs-deployreads the artifact instead of hardcodinghas-changes=true. Version branches keep current behavior via the existinguse-release-branchesoverride indocs-build.docs-build.yml: Uploadeffective_any_modifiedasdocs-build-check-metadataartifact from thecheckjobdocs-deploy.yml: Download the artifact in preflight; read the value for push events with fallback totrueon any failureTest plan
9.4) → pipeline runs regardless🤖 Generated with Claude Code