A push mirror is a one-way sync: whenever your repository changes, APIGit forwards its commits, branches and tags to a remote repository, keeping that copy up to date.
Push mirrors are often used for backup and redundancy, and to keep a copy of an API repository on the Git platform that another team or partner uses. Your APIGit repository stays the source of truth.
Push mirrors are available on the Enterprise plan. Navigate to your repository, open the Settings tab and go to Push Mirrors.

Click Add Push Mirror, then enter the remote address, how to authenticate, and the sync interval.

You can add several push mirrors to one repository. The target can be a popular platform such as Github, Gitlab, Bitbucket, Azure, AWS, Gitee, or even a self-hosted Git server with public access. If you want your external server to be the source of truth instead, see two-way sync.

You might get an error message if you use username and password to set upstream push mirrors for github repository.
In this case, you need a access token.
remote: Support for password authentication was removed on August 13, 2021. remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication. fatal: Authentication failed for https://github.com/tuasxxxx/test.git
Edits in APIGit now stay as drafts across files. Review them together, choose what goes in, and commit them as one commit, with conflicts resolved line by line.
Commit events in the timeline, a file tree for the diff, update branch, a merge style dropdown and checks that recover from temporary failures.
Clone and push over SSH at git.apigit.com, give a server access to one repository with a deploy key, and use personal access tokens limited to repositories.
Join thousands of developers and teams who are already using APIGIT to streamline their API development workflow.