Skip to content

neo-cowsay

Actions
Wraps some messages by neo-cowsay
v1.0.3
Latest
Star (5)
 _________________
< github action!! >
 -----------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

Actions Status

Powerd by 🐮 Neo-cowsay

Synopsis

Create Your Workflow

jobs:
  test:
    runs-on: ubuntu-latest
    name: A test job to cowsay
    steps:
    - name: output the message on actions result
      uses: Code-Hex/neo-cowsay-action@v1
      with:
        message: | # Support multi-lines
          This is cowsay
          Hello, World!!
    - name: cowsay on the comment
      uses: Code-Hex/neo-cowsay-action@v1
      with:
        message: 'Hello, World with random'
        cow: 'random' # If specified, it shows random ascii art.
        cowsay_on_comment: true
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    - name: output pipeline
      id: cowsay_output_id # You want id
      uses: Code-Hex/neo-cowsay-action@v1
      with:
        message: 'Hello, World'
        cow: 'gopher' # ascii art list: https://github.com/Code-Hex/Neo-cowsay/tree/master/cows
        cowsay_to_output: 'cowsay'
    - name: print output
      run: |
        echo "${{ steps.cowsay_output_id.outputs.cowsay }}"

See Example usage

Inputs

  • message - (Required) the message. what does the cowsay.
  • cow - (Optional) specify the cowfile.
    • default: default
    • if you specify random, cowsay shows by random ascii-art.
  • cowsay_on_comment - (Optional) boolean. if true, cowsay shows on the github comment.
    • this input needs to set the GITHUB_TOKEN environment variable.
  • cowsay_to_output - (Optional) specify the output_id.

neo-cowsay is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

About

Wraps some messages by neo-cowsay
v1.0.3
Latest

neo-cowsay is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.