sync workflows: merge PRs immediately instead of using --auto#90
Merged
developersdigest merged 1 commit intomainfrom Apr 10, 2026
Merged
sync workflows: merge PRs immediately instead of using --auto#90developersdigest merged 1 commit intomainfrom
developersdigest merged 1 commit intomainfrom
Conversation
gh pr merge --auto requires branch protection with required status checks on the target branch. firecrawl-claude-plugin and firecrawl-cursor-plugin don't have that configured, so the workflows fail with "Protected branch rules not configured for this branch (enablePullRequestAutoMerge)" after successfully creating the PR. There's nothing to wait for on a sync PR anyway, so drop --auto and merge immediately.
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.
gh pr merge --auto requires branch protection with required status checks on the target branch. firecrawl-claude-plugin and firecrawl-cursor-plugin don't have that configured, so the workflows fail with "Protected branch rules not configured for this branch (enablePullRequestAutoMerge)" after successfully creating the PR.
There's nothing to wait for on a sync PR anyway, so drop --auto and merge immediately.