git push newremote refs/remotes/oldremote/*:refs/heads/*

This command will push all branches from the oldremote to the newremote. The refs/remotes/oldremote/* part specifies that we want to push all branches from the oldremote, and the refs/heads/* part specifies that we want to push them to the newremote as branches.

For tags, that would not be so much complex, just git push newremote --tags would be enough.

Found at https://www.metaltoad.com/blog/git-push-all-branches-new-remote.

When working with multiple remote repositories, especially when syncing changes from upstream (such as in a forked repository), it’s important to have a well-structured system for organizing and tracking branches. This ensures clarity, ease of maintenance, and the ability to manage branches effectively. In this post, we’ll walk through the decision-making process for setting up a clear naming convention and syncing branches between your repository and an upstream one.

If you have multiple SSH keys and want to use a specific one for a particular Git repository, you can do so by configuring it on the SSH config file:

If you have a folder with multiple repositories that you want your commits use a different email account, but keep using your (personal) one for anything else, you can do it in two steps: