Skip to content

fix: reduce docs-noob-tester scope to prevent timeout #23742

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
pelikhan merged 3 commits into from
Mar 31, 2026
+25 −31
Merged

fix: reduce docs-noob-tester scope to prevent timeout #23742

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f12cb1b
Initial plan
Copilot Mar 31, 2026
f1b4233
fix: reduce docs-noob-tester scope to prevent timeout (#23734)
Copilot Mar 31, 2026
1fcf7f9
fix: use more directive wording for page visit limit
Copilot Mar 31, 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
36 changes: 19 additions & 17 deletions .github/workflows/docs-noob-tester.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

20 changes: 6 additions & 14 deletions .github/workflows/docs-noob-tester.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ permissions:
issues: read
pull-requests: read
engine: copilot
timeout-minutes: 30
timeout-minutes: 45
runtimes:
node:
version: "22"
Expand All @@ -34,6 +34,7 @@ network:
imports:
- shared/docs-server-lifecycle.md
- shared/reporting.md
- shared/keep-it-short.md
features:
copilot-requests: true
---
Expand All @@ -54,12 +55,11 @@ Act as a complete beginner who has never used GitHub Agentic Workflows before. B

## Step 1: Build and Serve Documentation Site

Navigate to the docs folder and build the documentation site using the steps from docs.yml:
Navigate to the docs folder and start the documentation site:
Comment on lines 56 to +58
Copy link

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Step 1 heading still says "Build and Serve Documentation Site", but the build step was removed and the instructions now only install deps and start the dev server via the shared lifecycle. Please rename the heading (and any nearby wording that implies a separate build step) so the instructions match what the agent is expected to do.

See below for a potential fix:

Act as a complete beginner who has never used GitHub Agentic Workflows before. Set up and navigate the documentation site, follow tutorials step-by-step, and document any issues you encounter.

## Step 1: Install Dependencies and Serve Documentation Site

Navigate to the docs folder and install dependencies:

Copilot uses AI. Check for mistakes.

```bash
cd ${{ github.workspace }}/docs
npm install
npm run build
```

Follow the shared **Documentation Server Lifecycle Management** instructions:
Expand Down Expand Up @@ -114,7 +114,7 @@ mcp__playwright__browser_run_code({
})
```

Using Playwright, navigate through the documentation site as if you're a complete beginner:
Using Playwright, visit exactly these 3 pages and stop:

1. **Visit the home page** at `http://${SERVER_IP}:4321/gh-aw/`
- Take a screenshot
Expand All @@ -136,15 +136,7 @@ Using Playwright, navigate through the documentation site as if you're a complet
- Note: Are the most important commands highlighted?
- Note: Are examples provided for common use cases?

4. **Explore Creating Workflows guide** at `http://${SERVER_IP}:4321/gh-aw/setup/creating-workflows/`
- Take screenshots of confusing sections
- Note: Is the workflow format explained clearly?
- Note: Are there enough examples?

5. **Browse Examples section**
- Visit at least 2-3 example pages
- Take screenshots if explanations are unclear
- Note: Can you understand how to adapt examples to your own use case?
After visiting all 3 pages, immediately proceed to the report.

## Step 3: Identify Pain Points

Expand Down Expand Up @@ -223,7 +215,7 @@ Follow the shared **Documentation Server Lifecycle Management** instructions for
## Success Criteria

You've successfully completed this task if you:
- Navigated at least 5 key documentation pages
- Navigated exactly 3 key documentation pages
- Identified specific pain points with examples
- Provided actionable recommendations
- Created a discussion with clear findings and screenshots
Expand Down
Loading