special actions. 注解 Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command- line use [https://docs.github.com/en/g

special actions. 注解: Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command-line use. For bigger setups, it is usually

special actions. 注解 Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command- line use [https://docs.github.com/en/g

special actions. 注解 Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command- line use [https://docs.github.com/en/g

special actions. 注解: Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command-line use. For bigger setups, it is usually

special actions. 注解: Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command-line use. For bigger setups, it is usually

special actions. 注解 Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command- line use [https://docs.github.com/en/g

special actions. 注解 Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command- line use [https://docs.github.com/en/g

special actions. 注解: Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command-line use. For bigger setups, it is usually

special actions. 注解 Depending on your setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user chosen branch. For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see Creating an access token for command- line use [https://docs.github.com/en/g