Use Claude Code, Codex, VSCode, Pi, and OpenCode (and 6 other harnesses) for free (1.3B+ free tokens) from your terminal, app, IDE, or phone, and now from the browser with native browser sessions (multi-harness + multi-model) like OpenClaw (voice supported + ToS friendly)
Python
Run CI for every pull request (#1429)
Ali Khokhar1200cdd8cc05
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.ymlindex ccb8f94a..7de43c51 100644--- a/.github/workflows/tests.yml+++ b/.github/workflows/tests.yml@@ -11,7 +11,6 @@ env:on:pull_request:- branches: [main]concurrency:group: ${{ github.workflow }}-${{ github.ref }}diff --git a/AGENTS.md b/AGENTS.mdindex 0ad67e6d..cbf4caaf 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -18,7 +18,7 @@- Do not add `# type: ignore` or `# ty: ignore`; fix the underlying type issue.- Do not add `from __future__ import annotations`; Python 3.14 native lazy annotations are the project standard.- All 5 check IDs are represented in `scripts/ci.sh` / `scripts/ci.ps1` and enforced by `tests.yml` before each merge (parallel jobs: suppression grep, ruff-format, ruff-check, ty, pytest).-- GitHub CI runs only for pull requests targeting `main`. Strict required checks keep each PR current with `main`, so the tested PR tree is the tree squash-merged without a duplicate post-merge run.+- GitHub CI runs for every pull request, including stacked PRs targeting non-`main` branches. Head updates trigger fresh checks; strict required checks keep PRs targeting `main` current with `main`, so the tested PR tree is the tree squash-merged without a duplicate post-merge run.- Repository protection should use rulesets: a non-bypassable main integrity ruleset requires pull requests and strict required checks, keeps branches current, and blocks direct/force pushes to `main`; a separate review ruleset may allow `Alishahryar1`/admins to bypass review only.- Required status checks: set **required status checks** to **all** of those statuses (e.g. **Ban suppressions and legacy annotations**, **ruff-format**, **ruff-check**, **ty**, **pytest**—use the exact labels GitHub shows, which may be prefixed with **CI /**). Remove **ci** from required checks if it was previously added for the old gate job.diff --git a/CLAUDE.md b/CLAUDE.mdindex 0ad67e6d..cbf4caaf 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -18,7 +18,7 @@- Do not add `# type: ignore` or `# ty: ignore`; fix the underlying type issue.- Do not add `from __future__ import annotations`; Python 3.14 native lazy annotations are the project standard.- All 5 check IDs are represented in `scripts/ci.sh` / `scripts/ci.ps1` and enforced by `tests.yml` before each merge (parallel jobs: suppression grep, ruff-format, ruff-check, ty, pytest).-- GitHub CI runs only for pull requests targeting `main`. Strict required checks keep each PR current with `main`, so the tested PR tree is the tree squash-merged without a duplicate post-merge run.+- GitHub CI runs for every pull request, including stacked PRs targeting non-`main` branches. Head updates trigger fresh checks; strict required checks keep PRs targeting `main` current with `main`, so the tested PR tree is the tree squash-merged without a duplicate post-merge run.- Repository protection should use rulesets: a non-bypassable main integrity ruleset requires pull requests and strict required checks, keeps branches current, and blocks direct/force pushes to `main`; a separate review ruleset may allow `Alishahryar1`/admins to bypass review only.- Required status checks: set **required status checks** to **all** of those statuses (e.g. **Ban suppressions and legacy annotations**, **ruff-format**, **ruff-check**, **ty**, **pytest**—use the exact labels GitHub shows, which may be prefixed with **CI /**). Remove **ci** from required checks if it was previously added for the old gate job.