ci(docs): label docs PRs pipecat-cloud - #203
Merged
Merged
Conversation
The docs PR this workflow opens was labelled `pipecat`, carried over from the workflow it was adapted from. Labels in pipecat-ai/docs name the source repo — `pipecat`, `pipecat-cloud` — so every docs PR from here was filed under the wrong one. Caught on the first real run: docs#1184, opened for PR #200, came through tagged `auto-docs, pipecat`.
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
1 participant
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.
One-word fix. The docs PR this workflow opens was labelled
pipecat, carried over from the workflow it was adapted from.Labels in
pipecat-ai/docsname the source repo —pipecat,pipecat-cloud— so every docs PR from this repo was being filed under pipecat's label.Caught on the first real run: docs#1184, opened for PR #200, came through tagged
auto-docs, pipecat.Matching fixes are on the two client-repo workflow PRs, which use a new
pipecat-client-weblabel covering bothpipecat-client-webandpipecat-client-web-transports— they publish into the same docs directory and split ownership by file, so one label keeps the pair findable together. (The existingclientlabel is a different axis: it covers iOS, Android, and React Native too.)🤖 Generated with Claude Code