Clone a specific Git branch#275
Conversation
swissspidy
left a comment
There was a problem hiding this comment.
Looks reasonable to me 👍 Thanks!
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #275 +/- ##
============================================
+ Coverage 72.24% 72.35% +0.11%
- Complexity 0 410 +410
============================================
Files 28 28
Lines 1250 1248 -2
============================================
Hits 903 903
+ Misses 347 345 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hey @swissspidy, I was wondering what’s still needed to move forward with version 4.0.0. It looks like some issues have been open for quite a while (since 2018–2019), and another PR got some pushback in 2022. A few of the already closed PRs also seem quite relevant, like the one improving PHP 8+ compatibility. Is there anything I could do to help get things moving again? |
|
I'll defer to @ocean90 as the maintainer. |
Co-authored-by: Dominik Schilling <dominikschilling+git@gmail.com>
|
FWIW I opened #278 to fix the GitHub Actions workflows. |
Description
This PR adds support for specifying a custom Git branch when triggering a translation build in Traduttore.
Motivation
Currently, Traduttore assumes that translations are always built from the repository’s default branch. This can be limiting in scenarios where a different branch needs to be translated—for example, feature branches or specific release branches.