Add "[skip ci]" to MantisBT commit messages

We don't currently have the ability to change the commit message per project [1], but we would like to find a solution. Are there any other ways to achieve the same end result?

As long as l10n changes are pushed directly to the master branch, I can't think of any way to bypass the TravisCI builds externally.

One alternative solution could be, as Verdy_p suggested, to have TWN push the changes to a separate branch, that we could exclude from automatic builds (blacklist). We would then have to manually merge changes into master. Maybe a Pull request could be opened to notify us that new translations are available. That involves some extra work on our end to manually merge changes, so it's a regression compared to the current situation but I guess we could adapt and live with that.

Another option (just brainstorming here) - assuming there is some existing API allowing that, we could pull changes and automate this on our end but that sounds like a lot of work.

Considering that the [skip ci] option is quite standard nowadays, and supported by most if not all of the main CI providers including GitHub Actions, Gitlab Pipelines, CircleCI and TravisCI, I believe that the best solution would be to implement some project-specific flag in the TWN config (repoconfig.yaml ?) to control whether [skip ci] is tagged at the end of the standard commit message.

Not being familiar with how that works internally, I have no idea if that's feasible or how complex it would be to implement.

Isn't there also the option to change the scheduling for exports from TWN and imports to Git? Projects have the option to define when they occur. May be the current scheduling is troo frequent (twice a week by default) and could be changed (once a week for example, so that you'll also reduce the frequency of automated builds in Travis, if this becomes now too costly).

Using branches for imports in Git IMHO is the best solution if you want to preserve the frequency (and possibly even increase it, e.g. each day) it does not prevent setting up another Git-specific bot if needed to sync that branch to the master, witrh a bot that you can schedule as you want, pause and restart when needed, for example pausing it when you're stabilizing a version of your project for a coming release)

@Nike, your feedback on this would be appreciated.

I have captured the commit message customization request in this task: https://phabricator.wikimedia.org/T310142

For short term, would switching the commit mode from push-to-master to push-to-branch + automatic pull request help you?

Thanks Nike. I subscribed to the Phabricator ticket to stay informed of progress.

would switching the commit mode from push-to-master to push-to-branch + automatic pull request help you?

As far as I know, pull request submissions also trigger TravisCI builds, so I don't think that would make any difference in terms of credits consumption, unless there is a setting that can somehow prevent the builds to occur based on some criteria (user who submitted, branch name or whatever). I'll look into that.

Please do not change anything for now.