Verifying Transifex automatic commit behavior

Gaël Bonithon trash.paradise at protonmail.com
Wed May 22 08:48:34 CEST 2024


Hi Hunter,

Our commits triggered transifex updates for technical reasons (migration to gettext, addition of a missing xml tag that was blocking translations). Apart from that, i.e. normally, commits only trigger transifex updates if they modify (including deleting/adding) strings to be translated. Your commit does neither (if I haven't missed anything), so it's normal that it doesn't trigger a transifex update.

Cheers,
Gaël

On Wednesday, May 22nd, 2024 at 2:27 AM, Hunter Turcin <huntertur at gmail.com> wrote:

> Hey all,
> 
> I'm trying to get back in the swing of contributing to Xfce and am
> looking at finally putting out another release of Xfburn. However, I've
> forgotten how exactly the Transifex integration works, and I would like
> to verify some behavior before I put out the release.
> 
> Take a look at the commit history for the Xfburn project:
> https://gitlab.xfce.org/apps/xfburn/-/commits/master
> 
> Historically, there are a large amount of commits pushed by Transifex
> whenever there is a code change. For some examples, see the commits
> made by Gaël Bonithon on April 7, Bobby Rong on April 5, and me on
> March 5 2023. However, I noticed that the flood of Transifex commits
> did not follow the commit I made on April 25; there has only been one
> translation update since then. Given the historical floods of commits,
> I want to double-check if the lack of automatic updates from the most
> recent commit means I should wait longer, if I should reconfigure
> something, or if the behavior is expected.
> 
> Thanks,
> Hunter Turcin
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
> https://mail.xfce.org/mailman/listinfo/xfce4-dev


More information about the Xfce4-dev mailing list