Expand description
Submission of translations to the Translation Hub, and the GitHub sign-in it needs.
The GitHub token is kept in the OS keyring and never leaves the server: frontends only see the sign-in state and the account’s login.
Enums§
- Submit
Outcome - Result of trying to submit a translation.
Constants§
- HUB_
OVERRIDE_ 🔒VAR - Environment variable to submit to another repository (
owner/name) instead of the real hub. Debug builds only. - KEYRING_
GITHUB_ 🔒TOKEN - Name of the keyring entry holding the GitHub token.
- KEYRING_
SERVICE 🔒 - Service name of RPFM’s entries in the OS keyring.
Functions§
- account
- Login of the GitHub account the user is signed in as.
- hub_
repository 🔒 - Owner and name of the repository translations are submitted to.
- keyring_
entry 🔒 - Keyring entry holding the GitHub token.
- keyring_
error 🔒 - Explain keyring errors, as they’re usually about the system’s keyring being unavailable.
- sign_
in_ poll - Check a GitHub sign-in. Once approved, keeps the token in the OS keyring and the account’s login in the settings.
- sign_
in_ start - Start a GitHub sign-in with the device flow.
- sign_
out - Sign out of GitHub, deleting the stored token and login.
- submit
- Submit a saved translation to the Translation Hub, or update its open pull request.
- token 🔒
- Stored GitHub token, if the user is signed in.