fix: remove /update command from merge-bot (not supported for fork PRs) #38
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
Removed the entire
update-commandjob from the merge-bot workflow as it does not work for PRs from forks and never will due to GitHub security restrictions.Problem
The
/updatecommand was designed to automatically merge the base branch into PR branches. However, it fails for all fork PRs because:Current Behavior (Before This PR)
When users try
/updateon fork PRs, they get:This creates confusion and adds 369 lines of non-functional code.
Solution
Removed the entire
update-commandjob (369 lines deleted).Impact
✅ Benefits
ℹ️ For Contributors
To update your fork's PR branch:
Or use GitHub's "Update branch" button (available for some fork PRs).
The
/updatecommand only worked for same-repo branches anyway. Since most contributions come from forks, this feature was rarely usable.Alternative Approaches Considered
Files Changed
.github/workflows/merge-bot.yml- Removedupdate-commandjob (369 lines deleted)Testing
/mergecommand still works🤖 Generated with Claude Code