Maximum access by forked repos is inaccurate

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

What part(s) of the article would you like to see updated?

As noted in #22492, Maximum access by forked repos really means Maximum access for pull requests from forked repos.

But, beyond that, https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-forks-of-private-repositories says:

Available to private repositories only, you can configure these policy settings for organizations, or repositories.
...
Send write tokens to workflows from pull requests - Allows pull requests from forks to use a GITHUB_TOKEN with write permission.

Thus, the correct text would be Maximum access for pull requests to public repositories from forked repos.

I know that's a mouthful and too much to stick into a column heading, but the current text is fairly misleading and finding all the caveats is not fun.

Additional information

PowerDNS/pdns#12249 (comment)

[cmwilson21]

👋 @jsoref - Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

[nawed2611]

Hey, I would like to work on this

[jsoref]

I wouldn't suggest picking this up until the waiting for review label is removed.

If you're looking for something to pick up, might I suggest:
https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+author%3Ajsoref+label%3A%22help+wanted%22

[lucascosti]

Thanks for pointing this out, @jsoref. Because this was slightly complicated to implement, i've opened a PR to fix in #22730.