You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add output for arbitrary crowdin CLI commands #299
Is your feature request related to a problem? Please describe.
In our flow we need to read Crowd In branches to decide on the next steps. For it, we are using with.command: 'branch list'. Yet I cannot get output of command in the following steps.
Describe the solution you'd like
Extend outputs of action with extra field command_output so that users can handle output.
Describe alternatives you've considered
As blunt as it sounds I've tried adding output redirection to the file like this: with.command: 'branch list > out.txt' or command_args: '> out.txt'. Which obviously fails.
Additional context
I am trying to achieve something similar to native Crowd In + GH integration: pull every branch on Crowd In into respective localization branch in git.
Thank you so much! Honestly, I wasn't expecting it to be added so fast. At that point we've moved on to use CrowdIn CLI directly from our host machine. It was both due to inability to use command output from action + hard requirement to use Linux runners which was a bit of a deal breaker as our team has only self hosted macs at the moment.
But we may consider going back to using action upon extending our Crowd In automation
@r-chumachenko thank you for the details! About MacOS runners support - it's a known limitation for the GitHub Action type we use (container action), unfortunately. I investigated this some time ago in #261, but was unsuccessful.
Activity
andrii-bodnar commentedon Dec 23, 2025
I like the idea! We should probably combine it with the
--plainparameter to make the output more readable for machine and easier to process.feat: add command_output for arbitrary CLI commands
andrii-bodnar commentedon Jan 13, 2026
Hi @r-chumachenko,
The
command_outputoutput has been implemented and is available for testing (#302)You can try it out by using the action from the
feat/add-command-outputbranch:Please let us know if it works as expected for your use case. Any feedback is appreciated!
r-chumachenko commentedon Jan 14, 2026
Hi @andrii-bodnar ,
Thank you so much! Honestly, I wasn't expecting it to be added so fast. At that point we've moved on to use CrowdIn CLI directly from our host machine. It was both due to inability to use command output from action + hard requirement to use Linux runners which was a bit of a deal breaker as our team has only self hosted macs at the moment.
But we may consider going back to using action upon extending our Crowd In automation
andrii-bodnar commentedon Jan 14, 2026
@r-chumachenko thank you for the details! About MacOS runners support - it's a known limitation for the GitHub Action type we use (container action), unfortunately. I investigated this some time ago in #261, but was unsuccessful.
r-chumachenko commentedon Jan 14, 2026
Yeah, monitoring that issue as well. Thank you for your time and effort though ❤️