Скачать или смотреть How to Push to One Remote Repository Only in a Multi-Remote Git Setup

Learn how to manage multiple remote repositories in Git and prevent push errors caused by configuration conflicts. Discover strategies to fix unintentional pushes and how to set read-only remotes.
---
This video is based on the question https://stackoverflow.com/q/76330034/ asked by the user 'fpdragon' ( https://stackoverflow.com/u/500774/ ) and on the answer https://stackoverflow.com/a/76340260/ provided by the user 'fpdragon' ( https://stackoverflow.com/u/500774/ ) 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: Push to one remote repository only in a multi remote repository local repository

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.
---
Introduction

Managing multiple remote repositories in Git can be daunting, especially when an unfortunate push operation leads to unintended consequences. Recently, a user experienced confusion while using Git Extensions, particularly with an older version, which resulted in accidentally pushing their entire primary repository's history to a secondary repository. In this guide, we will explore this problem in-depth, analyze the mistakes made, and provide clear solutions for avoiding such situations in the future.

The Problem: Unintended Pushes to Secondary Repository

Imagine the scenario: you're working with two remote repositories—one primary and one secondary. You've been cherry-picking changes from the secondary and pushing them to your local environment, and everything seems to be in order. However, after performing a fetch, you discover that the secondary repository has unexpectedly received all the data from your primary remote repository. Now, you're left with a tangled mess and a slew of questions about what went wrong and, more importantly, how to fix it.

Here's a concise breakdown of the user's concerns:

Mistake: Why did the secondary repository end up with the primary's data?

Solution: How can the secondary repository be restored to its original state?

Prevention: Is it possible to set up a secondary remote as read-only to avoid similar issues?

Understanding the Mistakes Made

The Role of Git Configuration

Using an older version of Git Extensions (2.49) created a scenario rife with complications:

Bugs and Compatibility Issues: The user found that configurations in the Repository dialog window acted unpredictably. URLs sometimes changed without notice, leading to both remotes pointing to the same secondary repository.

Pushing to the Wrong Location: When the user intended to push to the primary repository, it inadvertently pointed to the secondary due to misconfigured settings. The visual feedback in Git Extensions misled them into thinking everything was fine.

Fixing the Issue

Fortunately, there are steps you can take to untangle the web created by the accidental push:

Inspect and Correct Remote URLs

Check Remote Settings: Open the remote repository settings in Git Extensions. Ensure both primary and secondary URLs are correctly set.

Remove Unwanted Commits: If you need to delete specific commits from the secondary repository:

Use the Gerrit server's web interface.

Navigate to the branches pushed inadvertently from the primary repository and choose to delete those branches. This will remove the unwanted commit tree.

Upgrade Your Tools

Update Git Extensions: Consider using a more recent version of Git Extensions. The newer versions often contain bug fixes and better functionality, which can help avoid these messy situations.

Portable Versions: As found by the user, using a portable version of Git Extensions can help as it usually runs without many of the system-based quirks found in older versions.

Preventing Future Issues

Setting Up Read-Only Remotes

Understanding Remote Permissions: While Git does not have built-in flags for making a remote repository read-only, you can achieve similar results:

Server-Side Configurations: Depending on the remote repository architecture (like GitHub or GitLab), configure permissions so that specific user roles only have read access.

Local Git Configuration: When adding a remote, you can document (or note) that it’s intended to be read-only—though this won't technically enforce it.

Practice Safe Pushing: Always double-check which remote repository is selected in the push dialog before proceeding. Familiarizing yourself with the UI will m