Synthèse
Quite some time ago git-fetch(1) learned to fetch from a group of remotes. The following command configures a group of remotes: git config set remotes.forks "origin upstream" When this is set up, you can git-fetch(1) from this "forks" group, and then all the remotes in that list are fetched from. This can be useful when you want to get the updates from a set of remotes in one go. git-push(1), however, was not able to use remote groups. In Git 2.55, this gap is closed and git-push(1) now accepts
Quite some time ago git-fetch(1) learned to fetch from a group of remotes. The following command configures a group of remotes: git config set remotes. forks "origin upstream" When this is set up, you can git-fetch(1) from this "forks" group, and then all the remotes in that list are fetched from. This can be useful when you want to get the updates from a set of remotes in one go. git-push(1), however, was not able to use remote groups.
In Git 2. 55, this gap is closed and git-push(1) now accepts a remote group too. For example if you want to push the main branch to the group mentioned above: Similar as with git-fetch(1), this command pushes the specified refs to each of the remotes in the group. Each remote is pushed independently and honors its own remote. .
push mapping and mirror settings. This feature was submitted by Usman Akinyemi, suggested by Junio C Hamano.
Source originale
git-scm.com
CORTEX