Skip to content

Fix broken anchor links in project-ops docs causing CI build failure #20173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mnkiefer merged 3 commits into from
Mar 9, 2026
Merged

Fix broken anchor links in project-ops docs causing CI build failure #20173

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
772daab
Initial plan
Copilot Mar 9, 2026
38362d1
Fix broken documentation anchor links in project-ops.mdx
Copilot Mar 9, 2026
7692947
Merge branch 'main' into copilot/fix-github-actions-workflow-f02a7b2d…
mnkiefer Mar 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/src/content/docs/patterns/project-ops.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,10 @@ In practice, this gives teams faster triage decisions, cleaner board state, stro
## Prerequisites

1. **A Project board** and copy the project URL. See [Creating a project](https://docs.github.com/en/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project#creating-a-project).
2. **A Project token** (PAT or GitHub App token). See [Authentication for Project Operations](#authentication-for-project-operations).
2. **A Project token** (PAT or GitHub App token). See [Project Token Authentication](#project-token-authentication).
3. **A field contract** (for example: Status, Priority, Team, Iteration, Target Date). See [Understanding fields](https://docs.github.com/en/issues/planning-and-tracking-with-projects/understanding-fields).

## Authentication for Project Operations
## Project Token Authentication

Project operations need additional authentication because the default `GITHUB_TOKEN` is repository-scoped and cannot access Projects APIs for read/write project operations.

Expand Down Expand Up @@ -74,7 +74,7 @@ Let's look at examples of these in action, starting with the [Project Board Summ

## Examples

### Project Board Summarizer (Read-only)
### Project Board Summarizer

Let's start with a simple agentic workflow that reviews project board state and generates a summary without applying any changes.

Expand Down Expand Up @@ -119,7 +119,7 @@ Running the agentic workflow generates a concise summary of project status. We c
<img alt="Workflow summary output generated by Project Board Summarizer" src="/gh-aw/images/projectops-read-summary_light.png" />
</picture>

### Project Board Maintainer (Write)
### Project Board Maintainer

Let's write an agentic workflow that applies changes to a project board based on issue content and context.
This workflow will run on new issues, analyze the issue and project state, and decide whether to add the issue to the project board and how to set key fields.
Expand Down Expand Up @@ -187,7 +187,7 @@ In production, keep the loop simple: issue arrives, agent classifies and propose

## Related documentation

- **[Authentication for Project Operations](/gh-aw/patterns/project-ops/#authentication-for-project-operations)**
- **[Project Token Authentication](/gh-aw/patterns/project-ops/#project-token-authentication)**
- **[Safe Outputs Reference](/gh-aw/reference/safe-outputs/)**
- **[Projects & Monitoring](/gh-aw/patterns/monitoring/)**
- **[IssueOps](/gh-aw/patterns/issue-ops/)**