Make WordPress Core

Opened 11 months ago

Last modified 3 months ago

#56150 new enhancement

Add GitHub Action job summaries to workflows

Reported by: desrosj's profile desrosj Owned by:
Milestone: 6.3 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: good-first-bug needs-patch
Focuses: performance Cc:

Description

In May, GitHub released Job Summaries for GitHub Actions, which allows markdown or raw HTML to be displayed on the workflow run summary page for jobs.

This ticket is for exploring ways to use this feature in the WordPress Core workflows to make it easier to understand the data and outcomes buried in each step's log output within a job.

Change History (5)

#1 @desrosj
11 months ago

  • Keywords good-first-bug added

Was chatting with @johnbillion a bit in Slack about how this feature could be utilized in Core. He shared one example from a project of his.

After some discussion, the most apparent place that this could be useful is within the PHPUnit workflow to display a table with data around how many:

  • tests were identified as risky.
  • tests were skipped.
  • tests encountered errors.
  • total tests were found.
  • assertions were made.
  • etc.

I'm marking this as good-first-bug as it's self-contained, and a great way to dig in to learn more about GitHub Actions.

This ticket was mentioned in PR #3013 on WordPress/wordpress-develop by sarahricker.


11 months ago
#2

  • Keywords has-patch added

This ticket was mentioned in Slack in #core by desrosj. View the logs.


9 months ago

#5 @desrosj
3 months ago

I think it would be great to use this feature as a way to surface the results of the performance testing introduced in [55459].

The data is submitted to an external dashboard and is visible within the logs, but having it presented as a job summary would be really neat. cc/@joemcgill @flixos90 @mukesh27

#6 @joemcgill
3 months ago

  • Focuses performance added
  • Keywords needs-patch added; has-patch removed
  • Milestone changed from Future Release to 6.3

I dig this idea. Thanks @desrosj!

Note: See TracTickets for help on using tickets.