This allows the Github action that merges translations to master to bypass branch protection rules, as it is pushing directly rather than creating a pull request. It also allows manually triggering the action, in case that is required.
Credit goes to @p2004a, big thanks for your help.
Note that the rebase from master job will need to be run after merging, to get these changes on the transifex-synchronization-source branch, which is where the merge action runs.
The secret still needs to be created by a repository admin, so currently the action will not work.
This allows the Github action that merges translations to master to bypass branch protection rules, as it is pushing directly rather than creating a pull request. It also allows manually triggering the action, in case that is required.
Credit goes to @p2004a, big thanks for your help.
Note that the rebase from master job will need to be run after merging, to get these changes on the
transifex-synchronization-sourcebranch, which is where the merge action runs.The secret still needs to be created by a repository admin, so currently the action will not work.