Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
353741d
Initial plan
Copilot Sep 18, 2025
f259d07
Changes before error encountered
Copilot Sep 18, 2025
e65d73b
Implement Codex engine network permissions with interface-based valid…
Copilot Sep 18, 2025
baa9025
Refactor network validation to use interface-based approach for all e…
Copilot Sep 18, 2025
0a8ca91
Move network configuration to [sandbox] section in codex config.toml
Copilot Sep 18, 2025
4992ae5
Merge branch 'main' into copilot/fix-29e80832-c607-40a6-8348-bb735ae9…
dsyme Sep 18, 2025
ffa23d8
format
dsyme Sep 18, 2025
110fc57
Merge branch 'main' into copilot/fix-29e80832-c607-40a6-8348-bb735ae9…
dsyme Sep 18, 2025
4cc497c
Merge remote-tracking branch 'origin/main' into copilot/fix-29e80832-…
pelikhan Sep 19, 2025
0d218a3
Add GITHUB_AW_MCP_CONFIG environment variable to multiple workflow files
pelikhan Sep 19, 2025
2015174
Merge remote-tracking branch 'origin/main' into copilot/fix-29e80832-…
pelikhan Sep 23, 2025
6b73f9e
Refactor network access configuration in workflow files to use consis…
pelikhan Sep 23, 2025
81ede6d
Implement proper Codex sandbox modes and network access configuration
Copilot Sep 23, 2025
35af294
Add test agentic workflows demonstrating Codex network permission fun…
Copilot Sep 23, 2025
c316537
Add workflows for testing Codex with network restrictions
pelikhan Sep 23, 2025
a7f37d6
Remove unused branch trigger for pelikhan in dev workflow
pelikhan Sep 23, 2025
d0053ee
Update workflow configurations to enable output file persistence and …
pelikhan Sep 23, 2025
f250243
Refactor workflow and documentation setup: streamline steps and updat…
pelikhan Sep 23, 2025
8eb92d3
Update output file paths to use the home directory for Codex history …
pelikhan Sep 23, 2025
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
1,106 changes: 311 additions & 795 deletions .github/workflows/dev.lock.yml

Large diffs are not rendered by default.

82 changes: 4 additions & 78 deletions .github/workflows/dev.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,87 +5,13 @@ on:
push:
branches:
- copilot/*
- pelikhan/*
safe-outputs:
staged: true
upload-assets:
create-issue:
title-prefix: "[docs] "
engine:
id: claude
max-turns: 50
engine: codex
network:
allowed: ["*"]
permissions: read-all
tools:
playwright:
bash:
- "cd *"
- "npm *"
- "node *"
- "curl *"
- "ps *"
- "kill *"
- "sleep *"
- "mkdir *"
- "cp *"
- "mv *"
steps:
- name: Checkout repository
uses: actions/checkout@v5

- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '24'
cache: 'npm'
cache-dependency-path: 'docs/package-lock.json'

- name: Install dependencies
working-directory: ./docs
run: npm ci

- name: Build documentation
working-directory: ./docs
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: npm run build
---

# Documentation Build and Accessibility Analysis

This workflow compiles the documentation, launches the development server, takes a screenshot, and performs accessibility analysis.

Please follow these steps:

## Step 2: Build and Launch Documentation Server
0. Go to the `docs` directory
1. Start the documentation development server using `npm run dev`
2. Wait for the server to fully start (it should be accessible on `http://localhost:4321/gh-aw/`)
3. Verify the server is running by making a curl request to test accessibility

## Step 3: Take Screenshot with Playwright
1. Use Playwright to navigate to `http://localhost:4321/gh-aw/`
2. Wait for the page to fully load
3. Take a full-page screenshot of the documentation homepage
4. Save the screenshot to a file (e.g., `/tmp/docs-screenshot.png`)

## Step 4: Upload Screenshot
1. Use the `upload asset` tool from safe-outputs to upload the screenshot file
2. The tool will return a URL for the uploaded screenshot that can be included in the issue

## Step 5: Accessibility Analysis
1. Analyze the screenshot **image** for accessibility issues. DO NOT ANALYZE THE HTML. Focusing on:
- Color contrast ratios (WCAG 2.1 AA requirements: 4.5:1 for normal text, 3:1 for large text)
- Text readability against background colors
- Navigation elements visibility
- Button and link contrast
- Code block readability
- Overall visual hierarchy and accessibility

## Step 6: Create Issue with Results
1. Use the `safe-outputs create-issue` functionality to create a GitHub issue
2. Include in the issue:
- The uploaded screenshot URL from step 4
- Detailed accessibility analysis results
- Any recommendations for improvements

Focus on providing a comprehensive accessibility analysis that would be useful for improving the documentation's usability for all users.
Summarize the description of https://microsoft.com/
Loading