Cannot get Weblate to create a PR (500 error on Repository maintenance page)

[cg-tw]

Hello,
I'm using Weblate on a docker on my machine and I want it to create PRs directly on the repo when I push.

I have entered my username and fine-grained token in the WEBLATE_GITHUB_CREDENTIALS docker environment variable.

However, when I try to push a translation, it says: "Could not fork repository at api.github.com: Resource not accessible by personal access token". What have I done wrong? (BTW I don't want to fork the repo, just create a PR in it.)

If someone could point me in the right direction I would be very grateful.
Thank you.

[nijel]

Using personal access tokens for forking is problematic; see https://docs.weblate.org/en/latest/admin/config.html#std-setting-GITHUB_CREDENTIALS

If you would rather not fork, see https://docs.weblate.org/en/latest/admin/continuous.html#pushing-changes-from-weblate

[cg-tw]

Thank you for your response. I did find the doc page you mentioned and I followed what is written on it, yet it doesn't work. I followed the line in the table that says "GitHub pull request from branch".
So I don't understand the error message and why Weblate is trying to fork the repo. What can I do?

[nijel]

The thing I've fixed is just a display issue.

[cg-tw]

@nijel thank you very much for your help on this matter. I am glad this led to improvements or bugfixes. I have the feeling that the doc could be more explicit about some points, I'll see if I have time to list them.

[cg-tw]

I'm hoping this feedback helps improving the doc, helping other users in the future.

• it should be said explicitly that the correct name for the environment variable in a GitHub pull request context has the WEBLATE_ prefix in the "Code hosting sites credentials" section instead of only in the section for the weblate_github_credentials variable. (It says the example concerns GitHub pull requests but it gives GITHUB_CREDENTIALS as the environment variable to use, and when I used that it did NOT work. It does mention the weblate_ prefix when talking about Python dictionaries but it is not clear enough.)

• this section is not clear at all and just seems to contradict itself: https://docs.weblate.org/en/latest/faq.html#why-are-all-commits-committed-by-weblate-noreply-weblate-org

• in places the doc talks about "when you're using hosted weblate", but doesn't mention what you should do when you use it self-hosted (or is it supposed to be the next section? It is not stated clearly).

• this bit seems to suggest that just using a token is enough, which is incorrect https://docs.weblate.org/fr/weblate-5.12.1/vcs.html#github-repositories (the difference between "smaller deployments" and "bigger setups" is not explained. We did a small deployment but had to use the method for bigger setups as the other one wasn't working).

• in the user interface (and also the doc), the help text below the push url field is misleading: it says "laissez vide pour utiliser la branche du dépôt", i.e. leave empty to use the branch of the repo. I have been told it makes no sense as you cannot create a PR on the branch itself. Maybe the text makes sense when you are pushing directly to Git, not when you are opening a pull request (in that case it should say that the field is mandatory and not accept an empty value).

[nijel]

Improvements to the documentation are always welcome! I've created #16712 to track this for now.

[cg-tw]

Fantastic! Thank you very much ^^