New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement automatic upload of new content file on Develop to Crowdin #620

Closed
jordangriffiths01 opened this Issue Oct 13, 2017 · 1 comment

Comments

1 participant
@jordangriffiths01
Contributor

jordangriffiths01 commented Oct 13, 2017

When new/updated content markdown files are merged onto master, these need to be uploaded to Crowdin.

While Crowdin ships with GitHub integration, this is not suitable for this use case (see #619). Instead, this will probably need to be implemented as a Travis job that runs for new commits to master. Upload can be achieved through the Crowdin CLI (https://support.crowdin.com/cli-tool/).

@jordangriffiths01

This comment has been minimized.

Contributor

jordangriffiths01 commented Nov 23, 2017

After much discussion, it has been decided to upload new content from develop rather than master. This is because develop is essentially treated as a pre-release staging branch, and we will be merging new translations into develop so keeping it in one branch is cleaner.

@jordangriffiths01 jordangriffiths01 changed the title from Implement automatic upload of new content file on Master to Crowdin to Implement automatic upload of new content file on Develop to Crowdin Nov 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment