Skip to main content
Automate ASCII art creation on every push with a dedicated GitHub Actions workflow. Using cowsay, you’ll generate and display art in your CI logs, verify its output, and explore how ephemeral runners handle generated files.

1. Create the Workflow File

Under .github/workflows, create generate-ascii.yaml:

2. Workflow Steps Overview

Installing cowsay is crucial. Without it, any cowsay commands will fail.

3. Workflow Execution & Results

Once you commit and push, GitHub Actions triggers all workflows on push. In our example:
The image shows a GitHub Actions page with a list of workflow runs, including their status, branch, and action details. Some workflows are in progress, while others have completed with different outcomes.
  • The legacy workflow fails because it skips the cowsay install.
  • Generate ASCII Artwork completes successfully.

Installation Logs

Generate & Verify Art

List Workspace Files

4. Ephemeral Runner Environment

Art files like dragon.txt exist only on the runner VM. Once the job ends, the VM is torn down and all generated files are lost.
The image shows a GitHub repository page titled "actions-1" with a README file open, discussing GitHub Actions for automating workflows.

5. Disabling Unused Workflows

If you have multiple workflows on the same event, disable any you don’t need:
  1. Go to your repo’s Actions tab.
  2. Select the workflow to disable.
  3. Click Disable workflow.
This saves CI minutes and reduces clutter.

Watch Video