Skip to content

Add output for arbitrary crowdin CLI commands #299

Closed

Description

@r-chumachenko

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.

Activity

  1. andrii-bodnar commented on Dec 23, 2025

    @andrii-bodnar
    Member

    I like the idea! We should probably combine it with the --plain parameter to make the output more readable for machine and easier to process.

  2. added a commit that references this issue on Jan 13, 2026
    eab102d
  3. andrii-bodnar commented on Jan 13, 2026

    @andrii-bodnar
    Member

    Hi @r-chumachenko,

    The command_output output has been implemented and is available for testing (#302)

    You can try it out by using the action from the feat/add-command-output branch:

    - name: List branches
      id: crowdin
      uses: crowdin/github-action@feat/add-command-output
      with:
        command: 'branch list'
        # your other options...
    
    - name: Use command output
      run: echo "${{ steps.crowdin.outputs.command_output }}"

    Please let us know if it works as expected for your use case. Any feedback is appreciated!

  4. r-chumachenko commented on Jan 14, 2026

    @r-chumachenko
    Author

    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

  5. andrii-bodnar commented on Jan 14, 2026

    @andrii-bodnar
    Member

    @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.

  6. r-chumachenko commented on Jan 14, 2026

    @r-chumachenko
    Author

    Yeah, monitoring that issue as well. Thank you for your time and effort though ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions