Port to Drone 1.x and handle translations in this repo #7426
Conversation
|
|
dschmidt
force-pushed
the
2.6-l10n
branch
10 times, most recently
from
3ddab85
to
bf4fe5d
Compare
Before this was done in translation-sync repo because we had no drone cron jobs.
You might accidentally add, commit and push files not meant for public. Make sure your working directory is clean before testing this and possibly set a bogus remote name which will make the push fail.
The parameter is already unused as the target branch is determined by DRONE_BRANCH. This is okay, because the translation cron always triggers a specific branch.
|
@dschmidt Why is there a transifex commit in the PR? |
Basically "because the PR works" I configured the cron job so it runs on my branch. Probably I forked between a commit and the next transifex run, that's why there are a few changes. Subsequent runs did not trigger further commits as you can see: (also because I made the order of NSIS translations stable) When merged I will change the cron job to the 2.6 branch and raise the execution interval back to |
|
Ok! |
|
Please next time prefix your commit messages with the topic, e.g. "drone:" or "translations:" |
No description provided.