-
-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Solution] Upstream renamed from master
to main
#320
Comments
Will renaming the current branch to match the upstream repo's main branch work or do the app needs to do some algorithmic magic? |
@AndreiJirohHaliliDev2006 Yes but Git does not "rename" branches. Whatever git application you use is probably creating a new branch and deleting the old one. |
Dustin4444
added a commit
to Dustin4444/pull
that referenced
this issue
Mar 13, 2025
Fixes wei#320 Add documentation and comments to handle upstream branch renaming. * **README.md** - Add a section to inform users about the need to manually update the configuration file when the upstream branch is renamed. - Provide an example of how to update the `upstream` field in the configuration file to reflect the new branch name. * **src/utils/get-pull-config.ts** - Add a comment to indicate that the function does not handle branch renaming. * **.devcontainer/devcontainer.json** - Add a devcontainer configuration file with build and test tasks. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/wei/pull/issues/320?shareId=XXXX-XXXX-XXXX-XXXX).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the default configuration, Pull will/might stop working when upstream renames their default branch from
master
tomain
, or any other name.The easiest solution is to create a new branch called

main
like so:With this change, Pull app will automatically pull in upstream's
main
to yourmain
branch.You can then set the
main
branch as your new default branch (optional).The text was updated successfully, but these errors were encountered: