Repository navigation
fix(hub): fetch origin first in the GitHub trigger prompts - #3140
Merged
Merged
Conversation
New worktrees and branches then always start from the latest main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MichielMak
enabled auto-merge (squash)
October 25, 2026 09:49
MichielMak
approved these changes
Oct 25, 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
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
paseo-mentionandrenovate-needs-agentprompts now start withgit fetch origin, so new worktrees and branches always start from the latestmain. Already deployed to Hub withpaseo hub deploy; this PR puts it in git.🤖 Generated with Claude Code