DigitalSeneca
commented
1 month ago Maybe we can discuss about this topic more in detail/depth in a call to make a decision, but:
From the perspective of the app developer, in the current setup the most logic/comfortable would be to sync on the pull request that contain translations, or to get them in the v34 / v{x} branch, but maybe it's not the easiest to implement
At the moment, we’re using both GitHub tags and branches for each version
Maybe it's easier/simpler to change the workflow to remove the extra long-term branches (like v34) and target master so that we can synchronize Localise using Github Tags only instead of also new branches
epou
@DigitalSeneca I’d appreciate your thoughts on this. I’ve been considering the possibility of grouping string_ids in Localise, but the challenge is that Localise currently only supports grouping by tags. This led me to the idea of syncing GitHub tags with Localise tags, which would require us to establish a consistent tagging strategy in GitHub.
Another aspect I’m considering is automating pull requests based on specific actions—perhaps when a tag is created or when a new pull request is made, though I’m still exploring the best triggers to use.
At the moment, we’re using both GitHub tags and branches for each version, and I’m uncertain about which triggers would be most effective. I’d love to hear your perspective on this.