Replies: 1 comment
-
|
GitHub personal access tokens are tricky for forking and creating pull request. They need permissions for both sides of the fork/pull request, not just one of them. You might prefer not to fork when using PAT by setting push URL to repository URL in Weblate (see https://docs.weblate.org/en/latest/admin/continuous.html#pushing-changes-from-weblate). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to push "5 outgoing commits" from different projects and keep getting error messages that I don't know how to fix:
Both projects are using "GitHub pull request" as version control system. The source code repository is in the following format:
https://username:token@github.com/username/repo.git
The token is a repo specific fine grained access token with every read and write permission possible for repositories.
The push url is empty. The GitHub credentials in the docker compose file are set and I tried using a fine grained token (with all repositories) and a classic token (also with every permission). The weblate bot is added as contributor to the repositories. I also tried regenerating the tokens, but no success.
What am I missing here?
Beta Was this translation helpful? Give feedback.
All reactions