I have the GitHub integration set up and I’m noticing that PRs created using it have now appended [ci skip] to the commit messages by default. My crowdin.yml configuration doesn’t have anything related to the commit message format as documented here. In fact, based on that documentation.
This seems to have been happened sometime within the past week or so. Is this an intentional change? The relevant docs suggest that this is unexpected and some kind of regression.
Also, apologies if this was already mentioned elsewhere - I haven’t had a need to reach out to the forum to troubleshoot!
It’s expected. Some time ago, we added CI skip commit message to all connectors (depending on what is supported by the platform, GitHub, GitLab, Bitbucket, Azure, etc.) (CN-64013 int. number).
So every commit the GitHub connector makes, translations, source pushes, and crowdin.yml updates are now carried [ci skip] by default. It’s a server-side change that hasn’t been documented yet (we’ll be updating the docs soon).
Just for context, the decision to make [ci skip] default is a safeguard against infrastructure overload. Our integration commits each file individually via API; without this prefix, syncing 100 files would trigger 100 simultaneous CI pipelines. For the vast majority of users, this leads to unexpected costs and hits concurrency limits.
We believe it’s safer to skip these intermediate builds by default. Since translations are synced to a dedicated service branch, your CI will still run as expected once you create a Pull Request or merge those changes into your main branch. This ensures your final build is verified without wasting resources on every single file update.