docs(actions): fix incorrect statement regarding permissions & secrets

[monholm]

Why:

Read-only permissions and no access to secrets only applies to pull requests from forks.

Closes: #25117

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

The sentence regarding what permissions the workflow will have when triggered by the pull_request event.

Check off the following:

• I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
• For content changes, I have completed the self-review checklist.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[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/security-guides/security-hardening-for-github-actions.md	fpt ghec ghes@ 3.11 3.10 3.9 3.8 3.7 ghae	fpt ghec ghes@ 3.11 3.10 3.9 3.8 3.7 ghae

---

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

[cmwilson21]

@Simon-TechForm Thank you for opening a PR and linking it to your issue! ✨

I'll get this triaged for review! ⚡

[monholm]

@cmwilson21 I just stumbled upon the wording again, and still find it very unfortunate that a security hardening guide provides this false sense of security.

Any news on this PR? :)

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[jc-clark]

This looks good to me. Thank you for this contribution @monholm! ✨

I'll go ahead and merge this.

[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 ⚡