feat(ci): add work-in-progress label workflow for docs PRs#24950
Merged
feat(ci): add work-in-progress label workflow for docs PRs#24950
Conversation
Automatically adds a "work in progress" label when a PR is opened or reopened, and removes it when a member or owner approves the PR. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
Bot
added
the
domain: ci
pront
added
the
no-changelog
Target only PRs that touch docs-owned paths (matching CODEOWNERS) so the docs team isn't pinged until a Vector team member approves. The label is auto-added on open/reopen and auto-removed on first member approval. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pront
changed the title
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pront
changed the title
- Split single workflow into add_wip_label.yml and remove_wip_label.yml to avoid paths filter affecting pull_request_review events - Move association and label checks into github-script step instead of job if condition (GitHub Actions silently fails author_association checks in if expressions) - Tested end-to-end in vectordotdev/ci-sandbox Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a81a5f14a6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…later Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
thomasqueirozb
approved these changes
Apr 15, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
The docs on-call team gets auto-requested as reviewers (via CODEOWNERS) as soon as a PR is opened that touches doc paths. This means they see PRs that the Vector team hasn't finished reviewing yet, creating noise in their on-call list.
This workflow addresses that by:
work in progresslabel when a PR is opened or reopened that touches docs-owned paths (docs/,website/content/,website/cue/reference/)work in progresslabel from their on-call listSplit into two workflow files (
add_wip_label.ymlandremove_wip_label.yml) because combiningpull_request_targetwithpathsandpull_request_reviewin one file causes GitHub to apply the path filter to review events too.The association and label checks are done inside a
github-scriptstep rather than jobifconditions, asauthor_associationchecks silently fail inifexpressions.Vector configuration
N/A - CI workflow only.
How did you test this PR?
End-to-end testing in vectordotdev/ci-sandbox (PR 17).
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.Notes
work in progresslabel must exist in the repo (Settings > Labels) for the add step to succeed.add_wip_label.ymlmirror the@vectordotdev/documentationentries in.github/CODEOWNERS. Both files have comments pointing to each other to keep them in sync.