The Weblate Manual, Release 4.13 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.12.2 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.13.1 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

localization, Avoiding merge conflicts How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

localization, Avoiding merge conflicts How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

localization, Avoiding merge conflicts How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.11 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.12.1 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

localization, Avoiding merge conflicts How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.12 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public