8c2780d62c## Problem
- The `agama-weblate` repository has been also moved
## Solution
- Update the references in the GitHub Actions to use generic
`github.repository_owner` (the actions use
`!github.event.repository.fork` condition so they should never run
outside of the `project-agama` , but this is more flexible)
- Update the links in the documentation
## Notes
- I was thinking about using relative URLs in the documentation, but
then it would not work in forks (unless you fork the `agama-weblate`
repository as well). Absolute URLs are probably better here, I do not
expect we move the location anytime soon. 😃
22 lines
1,023 B
Markdown
22 lines
1,023 B
Markdown
# Translations
|
|
|
|
This directory contains translation files for the web frontend part of the Agama
|
|
installer. See more details in the main [i18n](../../doc/i18n.md) documentation.
|
|
|
|
## Contribution
|
|
|
|
:warning: *WARNING: Do not manually change any files here! The files are
|
|
automatically overwritten by the files from the
|
|
[agama-weblate](https://github.com/agama-project/agama-weblate/tree/master/web) Git
|
|
repository! Your changes would be lost on the next synchronization!* :warning:
|
|
|
|
For updating the translations use the [Agama Weblate
|
|
project](https://l10n.opensuse.org/projects/agama/agama-web/). The changes
|
|
in the Weblate are automatically saved to the agama-weblate repository
|
|
and later a pull request with the changes is automatically created for merging
|
|
the changes here.
|
|
|
|
Alternatively you can open a pull request against the
|
|
[agama-weblate](https://github.com/agama-project/agama-weblate/web) GitHub
|
|
repository. But that requires manual approving and merging, prefer using the
|
|
Weblate tool, it merges automatically.
|