Disable commits for GNOME Translation Robot <gnome-sysadmin@gnome.org> in dead branches
@mcrha
Submitted by Milan Crha Link to original bug (#750289)
Description
There just happened a commit [1], which was pushed into very old branches [2] by a translator, but it really doesn't make sense to do it there, because those branches are effectively dead - the only live branches, in case of evolution* products, are the master and the current stable branch, currently gnome-3-16. Furthermore, such translation commits in the branches like gnome-2-32 may rather break translations, because the source code is too different between 2.32 and 3.17, like the strings available in one are not in the other branch and vice versa, thus in some cases the translators can break old branches, rather than fix them, by removing still valid translatable strings in old branches.
I tried to contact the committer once he made it for the first time, but as his "effort" repeated, I do not know what to do to kindly ask him to avoid that.
My request is to either be able to tell the robot where it can commit or not per product, or better let commit translations only to the last two branches, the current stable and current master (maybe also per-product setting). This may limit only the commits through the "GNOME Translation Robot", other ways like committing into a local git checkout should not be rejected.
[1] https://git.gnome.org/browse/evolution/commit/?h=gnome-2-32&id=9349618e85 [2] affected branches: gnome-2-32 gnome-3-0 gnome-3-2 gnome-3-4 gnome-3-6 gnome-3-8 gnome-3-10 evolution-3-12 gnome-3-16 master