<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=19896) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=19896) </details> <!--IssueSummary end--> ## Goal To have an automatic trigger of the pipeline created in https://gitlab.com/gitlab-org/gitlab/-/issues/250314 so that we do not need manual intervention to get the translation MR ready to be merged. ### Pre-requisites This can be completed after we have: 1. Created a script(s) which can execute the steps we currently perform manually: https://gitlab.com/gitlab-org/gitlab/-/issues/23256 1. Created a pipeline that can be triggered manually: https://gitlab.com/gitlab-org/gitlab/-/issues/250314 ## Notes Investigation was completed into how we can achieve this here: https://gitlab.com/gitlab-org/gitlab/-/issues/227181#note_410472981 It looks like we have two main options for the trigger: #### Crowdin triggered We can set up the Crowdin integration to regularly push to the `i18n-master` branch. The possible intervals from the Crowdin integration are: 1. `10 20 30 40 50` minutes 1. `1 3 6 12 24` hours This will sync the translations, adding to the branch if it already exists or creating a new one if it's missing. #### GitLab triggered We can set up a [Pipeline Schedule](https://gitlab.com/help/ci/pipelines/schedules) to trigger our own pipeline on any schedule we want. This requires a target branch and currently we delete the `master-i18n` branch after every merge. It also doesn't look like there is an API endpoint on Crowdin for managing integrations. I think to get this working, we would have to leave the integration enabled and always have a `master-i18n` branch available (with a large number of commits). <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->