There was an error while loading. Please reload this page.
The dependency line was wrong, and init prints something else `apk add --no-cache bash curl git jq` installed a package the CLI never invokes and did not name the one it does. jq appears nowhere in the script. unzip is what unpacks the downloaded translations; alpine ships it as a busybox applet, so the job worked either way, but naming it keeps the recipe working if the image is ever swapped. git is there for the push step, not for the CLI, whose every git call is guarded and falls back. The Alpine note repeated the same list and claimed a bare alpine has none of those tools. Checked against alpine:3.22: bash, curl, git and jq are absent, unzip and sha256sum are present. The page also promised `init` prints exactly these recipes. It does not: the GitHub copy here adds a paths: trigger, and the GitLab copy adds a sha256sum check. Both are worth having, so they stay — now labelled as additions rather than passed off as the generated output. The GitHub comment calling paths: "the loop guard" is corrected too: the guard is the stable ptc/translations branch, and paths: is a second layer.
Add the CI/CD templates the docs promise; drop links customers cannot open ptc.wpml.org/documentation/ptc-api-reference/cicd-pipeline-setup sends readers here for 'the ready-made CI/CD configuration for your platform' and says the templates 'already include the steps to download and run the CLI'. This wiki had no templates at all — one link list, last touched in September 2025. Two of the six links pointed at git.onthegosystems.com, which is our internal GitLab and the projects there are private: every customer who clicked them got a login redirect. Removed, with a pointer to the GitLab job instead. CI-CD-templates now carries both recipes: the GitHub one through ptc-action, the GitLab one inline with the PTC_GIT_PUSH_TOKEN fallback and the [skip ci] guard, both pinned to v1.0.3 with the sha256 to verify against.