Consider adding an "Alternatives" section that shows the ternary hack

[jcbhmr]

Would be good to show why/when you should/could use this action instead of the ternary hack

steps:
  - uses: actions/checkout@v3
  - run: npm run build ${{ inputs.production && '--production' || '' }}
    # => adds '--production' if box is checked, '' if not

Other good things that could be linked to:

• Conditional operator or function for expression syntax actions/runner#409
• https://github.com/orgs/community/discussions/75928
• https://pablissimo.com/1137/github-actions-ternary-operators-and-default-values
• https://github.com/orgs/community/discussions/26738
• https://github.com/orgs/community/discussions/68534
• https://7tonshark.com/posts/github-actions-ternary-operator/

Want to explain and answer this question: Why would a user use this:

steps:
- uses: haya14busa/action-cond@v1
  id: condval
  with:
    cond: ${{ github.event_name == 'pull_request' }}
    if_true: "value for pull request event"
    if_false: "value for non pull request event"
- name: Use conditional value
  run: echo "${{ steps.condval.outputs.value }}"

instead of this?

steps:
  - run: echo "$VALUE"
    env:
      VALUE: |
        ${{ github.event_name == 'pull_request'
          && 'value for pull request event'
          || 'value for non pull request event }}

Something like "if you have a lot of chained if conditions this action is a good fit for you" or something would be quite helpful.

[jannikschaper]

Especially considering GitHub officially documents this feature as "ternary operator like behavior" (src):