#CI templates

Automate lint, build, and E2E checks so extension changes stay releasable.

Use CI to run the same quality gates on every pull request and release branch.

#CI capabilities

#Core pipeline stages

1. install dependencies
2. run lint/check commands
3. build browser targets
4. run automated tests (including Playwright where applicable)
5. upload artifacts/reports

#Minimal GitHub Actions example

name: ci

on:
  pull_request:
  push:
    branches: [main]

jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: pnpm/action-setup@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: pnpm
      - run: pnpm install --frozen-lockfile
      - run: pnpm lint
      - run: pnpm extension build --browser=chromium

#Build matrix example

strategy:
  matrix:
    browser: [chromium, firefox]
steps:
  - run: pnpm extension build --browser=${{ matrix.browser }}

#Playwright in CI

• install browsers in CI job (playwright install or equivalent)
• keep retries slightly higher on CI than local
• publish Playwright reports/artifacts for failed runs
• use dist/extension-js/<browser>/ready.json as readiness contract before launching Playwright
• avoid parsing human-readable logs in CI automation scripts
• prefer native readiness gates: extension dev --wait --browser=<browser> (watch/dev) or extension start --wait --browser=<browser> (production/start)
• for machine consumers, prefer --wait-format=json

#Example readiness gate

pnpm extension start --wait --browser=chromium --wait-timeout=60000 --wait-format=json

#Common pitfalls

• CI scripts diverging from local scripts over time
• building only one browser target while shipping to multiple engines
• missing artifact upload for failed E2E jobs
• mixing unpinned Node/package manager versions across workflows

This repository includes an E2E workflow example at:

• .github/workflows/e2e.yml

#Best practices

• Keep CI commands close to local scripts to reduce drift.
• Fail fast on lint/config errors before expensive browser jobs.
• Cache dependencies and browser binaries when possible.
• Version lock CI Node and package manager versions for reproducibility.

#Next steps

• Add or refine Playwright E2E tests.
• Review commands reference for script alignment.