Update default run-name triggered by pull_request event

[muzimuzhi]

Why:

Closes: #32266

What's being changed (if available, include any code snippets, screenshots, or gifs):

Update docs according to current behavior of GitHub Actions, in which the default run-name of workflow runs triggered by pull_request event, found on "Actions" tab, uses PR title, not commit message.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[muzimuzhi]

https://github.com/github/docs/actions/runs/8470303578/job/23207709363?pr=32267 failed with a TLS handshake timeout:

(newlines and indents added by me)

Error: buildx failed with: ERROR:
  failed to solve: node:20-alpine@sha256:bf77dc26e48ea95fca9d1aceb5acfa69d2e546b765ec2abfb502975f1a2d4def:
  failed to resolve source metadata for docker.io/library/node:20-alpine@sha256:bf77dc26e48ea95fca9d1aceb5acfa69d2e546b765ec2abfb502975f1a2d4def:
  failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/sha256:bf77dc26e48ea95fca9d1aceb5acfa69d2e546b765ec2abfb502975f1a2d4def":
  net/http: TLS handshake timeout

[nguyenalex836]

@muzimuzhi Thanks so much for opening a PR! I'll get this triaged for review ✨

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
actions/using-workflows/workflow-syntax-for-github-actions.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[SiaraMist]

Thanks so much for updating the docs @muzimuzhi, and for providing examples to verify your changes in the issue you opened. ✨

I just made a small edit to match our style guide, and I'll go ahead and get this merged.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡