machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. 1.11.1 Accessing repositories The VCS hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 110 Chapter

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. 1.11.1 Accessing repositories The VCS hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 110 Chapter

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. 1.11.1 Accessing repositories The VCS hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 110 Chapter

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 100 Chapter in the last step of the component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 100 Chapter in the last step of the component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories