Trigger docs-draft-writer pipeline on merge to main#3760
Merged
DrJosh9000 merged 2 commits intomainfrom Mar 18, 2026
Merged
Conversation
Extracts the PR number from the merge commit message and triggers the docs-draft-writer pipeline with the repo and PR number. The downstream pipeline checks for needs-docs/needs-changelog labels and generates documentation or changelog drafts as needed. The step is async and soft_fail so it never blocks or fails builds.
DrJosh9000
requested changes
Mar 17, 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.
When a PR merges to main, extract the PR number from the commit message and trigger the docs-draft-writer pipeline. The downstream pipeline checks for 'needs-docs' and 'needs-changelog' labels and exits early if neither is present.
The trigger is async and soft_fail, so it never blocks or fails the main build.
Description
This is an addition to the agent build pipeline. On merges to main, it triggers the downstream docs-draft-writer pipeline, which will check to see if the merged PR needs docs (based on the presence of a needs-docs label on the PR), and if so, will attempt to write them. The trigger step will soft-fail so as to avoid blocking the main pipeline in any way.
Context
https://linear.app/buildkite/issue/SUP-6223/test-and-iterate-on-real-prs
Verification
We should see the docs-draft-writer pipeline being triggered with the correct input params (repo and PR ID) on each merge to main.
Deployment
Nothing to deploy, just a pipeline change.
Rollback
If it causes any issues with the pipeline, simply revert the change.