Merge 5af601ff71 into ff7abcd0c3

Update README.md
Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>
2025-10-31 10:08:37 +08:00 · 2025-10-09 12:36:35 +02:00 · 2025-10-09 12:36:33 +02:00 · 2025-08-13 12:04:09 +02:00 · 2025-07-09 15:34:44 +02:00
1 changed files with 6 additions and 0 deletions
--- a/README.md
+++ b/README.md
@ -349,6 +349,12 @@ jobs:
 *NOTE:* The user email is `{user.id}+{user.login}@users.noreply.github.com`. See users API: https://api.github.com/users/github-actions%5Bbot%5D
 # Outputs
 The `checkout` action provides the following outputs that can be referenced in later steps:
 - `ref`, the Git ref that was checked out (not available if the checkout resulted in a detached `HEAD`)
 - `commit`, the SHA of the commit that was checked out
 # Recommended permissions
 When using the `checkout` action in your GitHub Actions workflow, it is recommended to set the following `GITHUB_TOKEN` permissions to ensure proper functionality, unless alternative auth is provided via the `token` or `ssh-key` inputs:
Author	SHA1	Message	Date
David Zuelke	4adf310d16	Merge `5af601ff71` into `ff7abcd0c3`	2025-10-09 12:36:35 +02:00
David Zuelke	5af601ff71	Update README.md Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>	2025-10-09 12:36:33 +02:00
David Zülke	89616df839	Undo head.ref to head.sha change That'd actually introduce a potential race condition.	2025-08-13 12:04:09 +02:00
David Zülke	2b2b6d210d	Document outputs in README.md And use ref, not sha, for the PR checkout example, so that the checkout does not result in a detached HEAD.	2025-07-09 15:34:44 +02:00