This brings your fork's default branch into sync with the upstream repository, without losing your local changes. Merge the changes from the upstream default branch - in this case, upstream/main - into your local default branch. $ git checkout main > Switched to branch 'main' > From > * main -> upstream/mainĬheck out your fork's local default branch - in this case, we use main. > remote: Compressing objects: 100% (53/53), done. $ git fetch upstream > remote: Counting objects: 75, done. Commits to BRANCHNAME will be stored in the local branch upstream/BRANCHNAME. For more information, see " Configuring a remote repository for a fork."Ĭhange the current working directory to your local project.įetch the branches and their respective commits from the upstream repository. Syncing a fork branch from the command lineīefore you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. You can set the -force flag to overwrite the destination branch. If the changes from the upstream repository cause conflict then the GitHub CLI can't sync. gh repo sync owner/cli-fork -b BRANCH_NAME To update the remote fork from its parent, use the gh repo sync -b BRANCHNAME subcommand and supply your fork and branch name as arguments. To learn more about GitHub CLI, see " About GitHub CLI." When you're working from the command line, you can use the GitHub CLI to save time and avoid switching context. GitHub CLI is an open source tool for using GitHub from your computer's command line. Syncing a fork branch with the GitHub CLI If the changes from the upstream repository cause conflicts, GitHub will prompt you to create a pull request to resolve the conflicts. Review the details about the commits from the upstream repository, then click Update branch. Ĭopyright © 2024 Popcorn Time Project - Released under the GPL v3 license.On GitHub, navigate to the main page of the forked repository that you want to sync with the upstream repository.Ībove the list of files, select the Sync fork dropdown menu. You should have received a copy of the GNU General Public License along with this program. See the GNU General Public License for more details. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. If you distribute a copy or make a fork of the project, you have to credit this project as the source. A new build release indicates this is a pre-release of the version.A new patch release indicates a bugfix or small change which does not affect compatibility.A new minor release indicates a normal change that maintains backward compatibility.A new major release indicates a large change where backward compatibility is broken.Releases will be numbered with the following format:Ĭonstructed with the following guidelines: and copy paste the following text in the editor and saveįor transparency and insight into our release cycle, and for striving to maintain backward compatibility, Popcorn Time will be maintained according to the Semantic Versioning guidelines as much as possible.Sudo ln -sf /opt/popcorn-time/Popcorn-Time /usr/bin/popcorn-time ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |