[wp-trac] [WordPress Trac] #64299: Output relevant URLs in GitHub Actions logs.
WordPress Trac
noreply at wordpress.org
Mon Nov 24 20:32:06 UTC 2025
#64299: Output relevant URLs in GitHub Actions logs.
------------------------------+----------------------------------------
Reporter: desrosj | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: Build/Test Tools | Version:
Severity: normal | Keywords: good-first-bug needs-patch
Focuses: |
------------------------------+----------------------------------------
Several GitHub Actions workflows are responsible for performing tasks
against pull requests in response to certain actions. However, because of
how actions run, it's not easy to determine what was performed by each
workflow run. This is compounded by the fact that events such as
`workflow_run` and `workflow_dispatch` don't always list a branch, pull
request, or commit as context.
A few examples:
- The `reusable-cleanup-pull-requests.yml` workflow closes pull requests
that mention a given ticket noted as `Fixed` in a commit message. The SVN
changeset, ticket, and the pull requests closed on GitHub should be noted
and linked.
- The `failed-workflow.yml` workflow automatically reruns a workflow once
to help rule out network-related failures. The workflow being rerun should
be noted and linked to.
- The `props-bot.yml` workflow collects props for a given pull request.
The pull request should be noted and linked.
- The `commit-built-file-changes.yml` workflow commits any missed changes
to built files under version control back to a pull request. The pull
request being updated should be noted and linked to.
Note: This list is not all inclusive. Each workflow should be examined for
any details that could be helpful to output into each workflow run log.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64299>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list