[PR #968] [MERGED] docs: Expand the GITHUB_TOKEN section #1708

Closed
opened 2026-03-01 21:52:20 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/968
Author: @gzur
Created: 1/26/2022
Status: Merged
Merged: 1/31/2022
Merged by: @mergify[bot]

Base: masterHead: github-token-docs


📝 Commits (3)

  • 8c51a06 docs: Expand the GITHUB_TOKEN section
  • 053cb1c docs: Add a note on leaking GITHUB_TOKEN through shell history
  • d918d55 Merge branch 'master' into github-token-docs

📊 Changes

1 file changed (+11 additions, -1 deletions)

View changed files

📝 README.md (+11 -1)

📄 Description

When I started using act, it kept failing because I was missing the GITHUB_TOKEN and I couldn't be bothered to figure it out.

I was unsure how to get this token, so I did some research and wanted to lessen the confusion of future users.

I believe this is such a common use-case that it bears spelling out.

Fixes #967


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/968 **Author:** [@gzur](https://github.com/gzur) **Created:** 1/26/2022 **Status:** ✅ Merged **Merged:** 1/31/2022 **Merged by:** [@mergify[bot]](https://github.com/apps/mergify) **Base:** `master` ← **Head:** `github-token-docs` --- ### 📝 Commits (3) - [`8c51a06`](https://github.com/nektos/act/commit/8c51a06eb70caf5b959f7a5e67427bb78e3015f7) docs: Expand the GITHUB_TOKEN section - [`053cb1c`](https://github.com/nektos/act/commit/053cb1c9aa0338d38fdbc921083acd935cc4ab05) docs: Add a note on leaking GITHUB_TOKEN through shell history - [`d918d55`](https://github.com/nektos/act/commit/d918d55cc91291c2a2e92b5ecea0b4d06a5dd00c) Merge branch 'master' into github-token-docs ### 📊 Changes **1 file changed** (+11 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+11 -1) </details> ### 📄 Description When I started using act, it kept failing because I was missing the `GITHUB_TOKEN` and I couldn't be bothered to figure it out. I was unsure how to get this token, so I did some research and wanted to lessen the confusion of future users. I believe this is such a common use-case that it bears spelling out. Fixes #967 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-01 21:52:20 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#1708
No description provided.