How to push to multiple git remotes at once. Useful if you keep mirrors of your repo.

100%

How to push to multiple git remotes at once. Useful if you keep mirrors of your repo.

✓ Published0🌍 Public

Last edited Feb 9, 2016

Created on Sep 1, 2021

This example demonstrates how to configure Git to push a single branch to multiple remote repositories simultaneously, using the command-line interface and manual edits to the `.git/config` file. It shows the `git remote set-url --add --push` command, which modifies the `remote.origin.pushurl` entry, and also covers per-branch push remotes via `branch.<name>.pushRemote` settings, plus fetching from all remotes with `git fetch --all` and merging via octopus merge. The code relies on standard Git APIs and configuration syntax.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 1115454

This example walks through setting up a remote Git repository, from creating a bare repo on a server to adding it as a remote and pushing local commits. It shows shell commands for `git --bare init`, `git remote add origin`, and `git push origin master`, along with the resulting `.git/config` changes. The text also explains the concept of a bare repository and how to track remote branches, using plain code blocks rather than a visualization library. The data source is the gist’s embedded shell session output.

Aalessioalex

64% match

Loading thumbnail…

Deploy to target branch (e.g. gh-pages)

This example shows a shell script that automates deploying a built `dist` folder to a target branch such as `gh-pages`. It uses Git commands, including `git subtree split` to isolate the `dist` directory and `git push origin` with a forced update to the remote branch. After pushing, it resets the local commit with `git reset --hard` and then pushes the original branch to the remote. The script relies solely on the Git command-line interface, with no JavaScript visualization libraries or data sources involved.

Aamazingandyyy

61% match

Loading thumbnail…

How to make git repo to be another's repo subfolder preserving history

This example shows a multi-step Git workflow for relocating an existing repository (`Proto`) into a subfolder of another repository (`Main`) while preserving full commit history. It demonstrates the use of `git checkout --orphan`, `git rebase`, and the history-rewriting command `git filter-branch --tree-filter` to move all files into `SRC/proto` across every prior commit. The process also addresses hidden files (like `.editorconfig`) and explains how to merge the two repositories via `git remote add` and a final `git rebase`. The source is a plain-text markdown guide with shell commands.

RRestuta

58% match

Loading thumbnail…

Git Tips and Tricls

This visualization presents a collection of Git command-line tips and tricks, sourced from a gist by MrSteve2. It displays the commands as text-based data, showing both the raw shell syntax and the intended purpose of each operation. The example uses plain text rendering without any specific charting libraries or APIs, relying on a straightforward textual layout to present the commands and their descriptions. The data is encoded directly in the gist file as a list of shell commands, such as using `git branch | grep -v master | xargs git branch -D` for cleaning up local branches, and `git config --global push.default current` for changing push behavior.

MMrSteve2

58% match

Loading thumbnail…

Gist 1b72416b70ed6ab1957e78c94a754f91

This visualization demonstrates a shell script that cleans a Git repository by removing local branches whose remote counterparts no longer exist. It shows the process of fetching all remote branches, identifying branches marked as “gone” via `git branch -vv`, and deleting them with `git branch -D`. The example uses command-line Git APIs for repository management, with output reflecting the sequential execution of these operations. The rendering approach is plain text output from the terminal, illustrating the practical workflow for tidying up stale branches after many pull requests are merged.

CCarlos-Augusto

57% match

Loading thumbnail…

The Gist to Clone All Gists

This example demonstrates a practical workflow for backing up or synchronizing a GitHub user’s public gists. It first clones every gist from a specified GitHub account over SSH, using a paginated API fetch to retrieve the list of gists and the Node.js `https` module to authenticate via an OAuth token. It then shows a complementary bash script that iterates through local directories, committing any changes with an empty message and pushing them back to their remote origins. The visualization highlights the interplay between the GitHub REST API and command-line Git operations for batch repository management.

Mmbostock

56% match

Loading thumbnail…

GIT delete merged branches

This example shows how to clean up a Git repository by deleting local branches that have already been merged into the current branch. It provides two implementations—one for Bash and one for Windows PowerShell—both using the `git branch --merged` command to list eligible branches, then filtering out protected branches like `master`, `main`, `dev`, and `develop` with `egrep` or `Where-Object`, and finally deleting the remaining ones via `xargs git branch -d` or `ForEach-Object { git branch -d }`. The code relies on standard Git command-line tools and does not use a charting library, as the “visualization” here is the terminal output of branch names before and after deletion.

IIvanBuljovcic

56% match

Loading thumbnail…

Gist 96829331ffd980ee6a4f3ab1196708f1

This visualization presents a structured Git cheat sheet, organizing commands into clear categories like configuration, local and remote branch management, and advanced operations. It demonstrates a comprehensive set of command-line workflows, including branching, merging, stashing, and comparing changes, each paired with practical usage examples. The rendering relies on standard Markdown code blocks and inline formatting to distinguish commands, comments, and options, providing a reference-style layout rather than a data-driven graphic.

JJaxonDvl

55% match