Скачать или смотреть How to Push an Existing Repo to a Fork on GitHub

Learn how to seamlessly push your existing Git repository to a fork of another repository while preserving your commit history.
---
This video is based on the question https://stackoverflow.com/q/65679790/ asked by the user 'Ravindu Fernando' ( https://stackoverflow.com/u/9149202/ ) and on the answer https://stackoverflow.com/a/65679825/ provided by the user 'Alex Baranowski' ( https://stackoverflow.com/u/3948711/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How do I push my existing repo to a fork of another repo?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Push an Existing Repo to a Fork on GitHub

If you find yourself in a position where you need to transfer your existing Git repository to a newly created fork for a project, you're not alone! Many developers face this challenge when their workplace decides to establish a central repository for collaborative work. In this guide, we'll walk through an efficient method to push your existing repository to the fork without losing any valuable commit history.

The Dilemma

Imagine you have been working diligently on a project with your own GitHub repository. Everything seems to be in order until your workplace requires you to send a pull request (PR) to a newly created central repository (a fork of the original). At this point, your instinct might be to clone this new repository and copy-paste all your project files into it. However, this method can lead to a significant drawback: you would lose all your previous commits, which are essential for tracking your work and contributions.

The Solution: Pushing Your Existing Repo

Fortunately, there is a better way to achieve this! Instead of copying the files, you can simply add a new remote to your existing repository. Follow these steps to accomplish this task effectively:

Step 1: Check Your Current Remotes

Before making any changes, it's essential to know your existing remote settings. Open your terminal and run the following command:

[[See Video to Reveal this Text or Code Snippet]]

This command will display the remote repositories associated with your current project. You might see something like this:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Add Your New Remote

Next, you will want to add the new fork repository as an additional remote. This is done using the git remote add command. Replace the repository URL with the one specific to your new fork:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Push Your Branch to the New Remote

Now that you have added the new remote, you can easily push your work to the forked repository without losing your commit history. Use the git push command, specifying the new remote and the branch you want to push:

[[See Video to Reveal this Text or Code Snippet]]

Why This Method Works

By adding the new remote repository instead of replacing your original files, you can:

Preserve your full commit history, which is crucial for tracking changes and contributions.

Easily switch between multiple remotes if needed, allowing for efficient collaboration.

Keep your workflow streamlined and organized.

Conclusion

Creating a smooth transition from your existing repository to a new fork doesn't have to be complicated. By following the steps outlined in this post, you can maintain your commits while adapting your project to meet new requirements. The key takeaway is to add a new remote and push directly, rather than copying files. Happy coding!