Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.18 directly. git merge -s ours origin/maintenance 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.18 directly. git merge -s ours origin/maintenance 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.18 directly. git merge -s ours origin/maintenance 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.17 directly. git merge -s ours origin/maintenance 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.16 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.16 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.16 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.16 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.16 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

Reporting issues in Weblate Weblate testsuite and continuous integration Data schemas Releasing Weblate Security and privacy Contributing to Weblate modules About Weblate License Change history Weblate 4.15 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: GitHub repositories