The same familiar functionality that powers pull requests, issues, and README files has come to GitHub Actions! We’re thrilled to announce GitHub Actions Job Summaries, which allow for custom Markdown content on the run summary generated by each job. Custom Markdown content can be used for a variety of creative purposes, such as:

  • Aggregating and displaying test results
  • Generating reports
  • Custom output independent of logs

Create summaries

Simply output Markdown content to a new environment variable we’ve introduced called $GITHUB_STEP_SUMMARY. Any Markdown content added to this file will then be displayed on the Actions run summary page. That’s it!

steps:   - name: Adding markdown     run: echo ‘### Hello world! :rocket:’ >> $GITHUB_STEP_SUMMARY

The behavior for adding Job Summaries is very similar to how the $GITHUB_ENV variable is used to define environment variables.

To make it easier for Actions authors to generate Job Summaries, we’ve also added a new helper utility to the @actions/core npm package.

import * as core from ‘@actions/core’ await core.summary   .addHeading('Test Results')   .addCodeBlock(generateTestResults(), “js”)   .addTable([    [{data: ‘File’, header: true}, {data: ‘Result’, header: true}],    [‘foo.js’, ‘Pass `✅` ’],    [‘bar.js’, ‘Fail `❌`’],    [‘test.js’, ‘Pass `✅`’]   ])   .addLink(‘View staging deployment!’, ‘https://github.com’)   .write()

With the new utility, authors can easily add individual lines or blocks of Markdown. We’ve also made it easy to generate tables, since we envision this being a very common scenario.

For more information, check out our full documentation for adding Job summaries.

Why these changes matter

Actions users have been asking for this type of functionality for a long time. User-generated content from Actions has previously been limited to logs and annotations. It can be difficult to aggregate and group lots of information. Annotations are important when it comes to highlighting things, like errors and warnings, and are not suited for rich output, like test summaries or build reports.

To get around these issues, we’ve even seen users manually create check runs using our API using the GITHUB_TOKEN that is provided as part of a run, which leads to decreased productivity. It’s clear that there’s been a feature gap, forcing users to improvise with less than ideal solutions, which is why we’ve developed Job Summaries!

Endless possibilities with the power of Markdown

The same familiar functionality that powers pull requests, issues, and README files has come to Actions! Actions Job Summaries support GitHub Flavored Markdown, which is incredibly powerful and allows users to create amazing workflows, as well as Actions to enhance their experience.

Below, are just a few examples of what we envision users doing with Job Summaries.

Running tests as part of CI is a very common scenario.

Good links and documentation can’t be understated.

Raw HTML and emojis galore

Markdown tables and hover cards with @mentions

Code blocks with copy/paste functionality

Mermaid, which has recently shipped, is very powerful!

We’d love to hear your thoughts!

At GitHub, we love to hear any feedback you have. Share your questions and comments with us in the GitHub Actions Community Forum.

We are excited about Job Summaries, and we can’t wait to see how the community will use them.

Thanks! ❤️