Event-Specific Details on the Actions tab

We have released an improvement to the Actions tab which makes it easier to distinguish workflow runs from each other. For example, you can now see the commit message associated with push events.

event specific details

The new information includes:

  • The workflow run number.
  • What triggered the workflow, which can be a release, a pull request, a push, an issue, a deployment… A link to it is provided as well.
  • A descriptive title based on what triggered the workflow. This can be the title of a pull request or an issue, the name of a release, the message of a commit, etc.
  • What action triggered the workflow. For example a pull request can be reopened, merged,… A release can be published, created or released. This value comes from the action field in the webhook payload that was triggered for the specific event.

This new information is available for new workflow runs. Older runs are not affected by this change.

You can now publish snapshots to the Apache Maven registry in GitHub Packages. This feature is enabled for all plans.

Learn more about Packages and Apache Maven

See more

IP allow lists are now generally available for GitHub Enterprise Cloud customers – allowing enterprise and organization owners to limit access to enterprise assets to an allowed set of source IPs. All authorization credential types, including personal access tokens and SSH keys, are filtered by IP allow lists for all apps, users, and roles with access to enterprise organizations. You may also use IP allow lists with GitHub Actions self-hosted runners.

Learn more about IP allow lists

See more