...
The .1 suffix is so that you can make a .2 if something needs to be fixed.
2b.
...
Fork the Transifex project
2b1 Double check the openedx-translations repository branch
Go to the https://github.com/openedx/openedx-translations repository and ensure it has the proper release branch e.g. you/test/z.1
.
2b2 Clone the openedx-translations Transifex project
After cutting the release e.g. zebrawood
a new Transifex project should be copied into a new project. This will ensure the translations sources and code source stay in sync after main
branches continue to evolve after cutting the release.
Create a new Transifex project: openedx-translations-zebrawood
Copy the resources from the old project (How to do that without ?)
2b3 Configure the GitHub Transifex App
This is a manual step:
Go to the Zebrawood Transifex project configuration settings
In the Integrations tab, click on the GitHub App integration “Manage” button
Click on the three dots
...
menu → the Settings buttonConfigure the project integrations settings from the main/master project (https://github.apps.transifex.com/projects/o:open-edx:p:openedx-translations/openedx/openedx-translations):
Select repo step:
Selected repository:
openedx/openedx-translations
Selected branch:
you/test/z.1
orrelease/zebrawood
Select files step:
Add a path to your YAML configuration file:
transifex.yml
Sync content step:
PULL CONTENT:
Fetch content automatically
PUSH CONTENT:
100% reviewed
How would you like Transifex to push translations to GitHub?
Create a Pull Request
andNo grouping
Add a prefix to the commit message:
chore:
Click on the Update Settings button
2c. Test the release one last time
...