Compare commits

..

3 Commits

Author SHA1 Message Date
Nikhil Sonti
1b4aaa75b6 fix(ci): show warning icon for zero-test suites instead of failure 2026-04-15 21:35:36 -07:00
Nikhil Sonti
25320458b9 fix(ci): use payload SHA for staleness check, handle missing artifacts
- Replace context.sha (merge commit SHA) with
  context.payload.pull_request.head.sha so the staleness guard
  compares the correct values and the comment actually gets posted
- Add continue-on-error to download-artifact so cancelled runs
  gracefully fall through to the "no test results" message
2026-04-15 21:05:40 -07:00
Nikhil Sonti
6f9da20fe1 fix(ci): add PR comment with test summary and block on failure
Add a `comment` job to the test workflow that parses JUnit XML artifacts
and posts a sticky PR comment showing pass/fail counts per suite, with
failed test names listed in a collapsible section and a link to the run.

Guards against fork PRs (read-only token) and stale overlapping runs
(skips comment if PR head has moved past our SHA).
2026-04-15 20:54:47 -07:00
2 changed files with 16 additions and 16 deletions

View File

@@ -75,24 +75,26 @@ packages/
### Setup
```bash
# Install dependencies, generate agent GraphQL output,
# and prepare WXT types for apps/agent
bun run dev-setup
Requires [process-compose](https://github.com/F1bonacc1/process-compose):
# Run the apps
bun run start:server
bun run start:agent
```bash
brew install process-compose
```
`bun run dev-setup` is a preflight command only. It does not manage `.env` files.
```bash
# Copy environment files for each package
cp apps/server/.env.example apps/server/.env.development
cp apps/agent/.env.example apps/agent/.env.development
cp apps/server/.env.production.example apps/server/.env.production
It runs the following in order:
# Start the full dev environment
process-compose up
```
The `process-compose up` command runs the following in order:
1. `bun install` — installs dependencies
2. `bun run codegen:agent` — generates agent GraphQL code
3. `bun run prepare:agent`generates WXT type output
If you want the broader dev harness after setup, use `bun run dev:watch`, `bun run dev:watch:new`, or `bun run dev:manual`.
2. `bun --cwd apps/agent codegen` — generates agent code
3. `bun --cwd apps/server start` and `bun --cwd apps/agent dev`starts server and agent in parallel
### Environment Variables

View File

@@ -10,7 +10,6 @@
],
"scripts": {
"postinstall": "bun run build:agent-sdk",
"dev-setup": "bun install && bun run codegen:agent && bun run prepare:agent",
"dev:watch": "./tools/dev/run.sh watch",
"dev:watch:new": "./tools/dev/run.sh watch --new",
"dev:manual": "./tools/dev/run.sh watch --manual",
@@ -27,8 +26,7 @@
"build:agent:dev": "FORCE_COLOR=1 bun run --filter @browseros/agent --elide-lines=0 build:dev",
"build:agent": "bun run codegen:agent && bun run --filter @browseros/agent build",
"build:agent-sdk": "bun run --filter @browseros-ai/agent-sdk build",
"codegen:agent": "bun --cwd apps/agent graphql-codegen --config codegen.ts",
"prepare:agent": "VITE_PUBLIC_BROWSEROS_API=${VITE_PUBLIC_BROWSEROS_API:-http://127.0.0.1:9105} bun --cwd apps/agent wxt prepare",
"codegen:agent": "bun run --filter @browseros/agent codegen",
"test": "bun run test:tools && bun run test:integration",
"test:tools": "bun run --filter @browseros/server test:tools",
"test:integration": "bun run --filter @browseros/server test:integration",