Repository navigation
ci: skip automatic PR description drafts for bot PRs - #283
Merged
Merged
Conversation
Dependabot PRs are same-repo, so the fork guard didn't catch them, and claude-code-action rejects bot actors. They also don't get repository secrets, so allowing the bot wouldn't help.
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.
The Draft PR Description workflow has Claude write a PR's description when the PR is opened. It fails on every Dependabot PR (for example #278), so those PRs show a red check that has nothing to do with the dependency bump. This change makes the automatic trigger skip PRs opened by bots.
claude-code-actionthen stops withWorkflow initiated by non-human actor: dependabot (type: Bot). The job'sif:now also requiresgithub.event.pull_request.user.type != 'Bot', so on these PRs the job is skipped instead of failing.allowed_bots. Workflows that Dependabot triggers don't get the repository's Actions secrets, soANTHROPIC_API_KEYis empty in these runs. Allowing the bot would only move the failure to the next step./pr-descriptionand/release-notescomments andworkflow_dispatchwork the same as before.This is the matching edit for the copy in pipecat-ai/pipecat-client-web-transports#262, which the workflow file says to keep in sync.