Skip to content

Commit 240db35

Browse files
authored
Reorder token configuration sections: Step-by-Step before Quick Start (#5)
1 parent 2466cc2 commit 240db35

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

README.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,6 @@ This repository is a template for creating GitHub Agentic Workflows. Agentic wor
99

1010
GitHub Agentic Workflows require specific tokens to authenticate with various services. GitHub Actions always provides `GITHUB_TOKEN` automatically, but for advanced features like Copilot workflows, you'll need to configure additional tokens.
1111

12-
### Quick Start: Tokens You Need to Configure
13-
14-
Create these repository secrets based on what features you need:
15-
16-
| When you need this... | Secret to create | Notes |
17-
|----------------------|------------------|-------|
18-
| Cross-repo operations / remote GitHub tools | `GH_AW_GITHUB_TOKEN` | PAT or app token with cross-repo access |
19-
| Copilot workflows (CLI, engine, agent tasks, etc.) | `COPILOT_GITHUB_TOKEN` | Needs Copilot Requests permission and repo access |
20-
| Assigning agents/bots to issues or pull requests | `GH_AW_AGENT_TOKEN` | Used by `assign-to-agent` and Copilot assignee/reviewer flows |
21-
| Any GitHub Projects v2 operations | `GH_AW_PROJECT_GITHUB_TOKEN` | **Required** for `update-project`. Default `GITHUB_TOKEN` cannot access Projects v2 API |
22-
| Isolating MCP server permissions (advanced optional) | `GH_AW_GITHUB_MCP_SERVER_TOKEN` | Only if you want MCP to use a different token than other jobs |
23-
2412
### Step-by-Step: Configuring Tokens for Copilot
2513

2614
Follow these steps to set up GitHub Copilot in your agentic workflows:
@@ -53,6 +41,18 @@ If you need additional capabilities, add these tokens as repository secrets foll
5341
- **For agent assignment operations**: Create a secret named `GH_AW_AGENT_TOKEN`
5442
- **For GitHub Projects v2 operations**: Create a secret named `GH_AW_PROJECT_GITHUB_TOKEN`
5543

44+
### Quick Start: Tokens You Need to Configure
45+
46+
Create these repository secrets based on what features you need:
47+
48+
| When you need this... | Secret to create | Notes |
49+
|----------------------|------------------|-------|
50+
| Cross-repo operations / remote GitHub tools | `GH_AW_GITHUB_TOKEN` | PAT or app token with cross-repo access |
51+
| Copilot workflows (CLI, engine, agent tasks, etc.) | `COPILOT_GITHUB_TOKEN` | Needs Copilot Requests permission and repo access |
52+
| Assigning agents/bots to issues or pull requests | `GH_AW_AGENT_TOKEN` | Used by `assign-to-agent` and Copilot assignee/reviewer flows |
53+
| Any GitHub Projects v2 operations | `GH_AW_PROJECT_GITHUB_TOKEN` | **Required** for `update-project`. Default `GITHUB_TOKEN` cannot access Projects v2 API |
54+
| Isolating MCP server permissions (advanced optional) | `GH_AW_GITHUB_MCP_SERVER_TOKEN` | Only if you want MCP to use a different token than other jobs |
55+
5656
## Creating Workflows
5757

5858
### Using the Create Agentic Workflow Agent

0 commit comments

Comments
 (0)