Relax preview-docs workflow trigger to run on any completion#19115
Merged
Relax preview-docs workflow trigger to run on any completion#19115
Conversation
Remove the success condition from preview-docs.yml so it triggers whenever docs.yml completes, regardless of success or failure. This allows previews to deploy even when lint checks fail, improving the feedback loop. The workflow will gracefully fail if build artifacts are not available. Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update preview-docs.yml trigger conditions
Relax preview-docs workflow trigger to run on any completion
Nov 30, 2025
harupy
approved these changes
Nov 30, 2025
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.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
The
preview-docs.ymlworkflow previously only triggered whendocs.ymlcompleted successfully. This blocked preview deployments when unrelated jobs failed (e.g., lint checks), slowing the feedback loop.Changes:
github.event.workflow_run.conclusion == 'success'condition from preview-docs workflowBehavior:
Since
checkandbuildjobs indocs.ymlrun independently, lint failures won't prevent successful builds from being previewed.How is this PR tested?
Validated YAML syntax with yamllint. The workflow behavior will be verified on the next PR that triggers docs.yml.
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
How should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.