Pull requests from forks can't talk their way past merge checks
On a pull request from a fork, only the author skip rule now skips Auditor merge checks: its branch name, title and missing opt-in label no longer do, since the person opening it chooses them. A required check that goes unjudged there, from a spend cap, no allowed model or an unclear verdict, fails the merge checks instead of leaving them neutral. Branches in the repository work as before.
Automations that run on a fork's pull request are now read-only, like @auditor fix and @auditor tests: they can read the change and comment, but never open a pull request or push from it.
Reviews of a fork's pull request no longer read the ticket it names from your tracker, write its title into the description, or comment on it, since anyone opening a fork could name a private ticket and see what it says. Static analysis there skips ESLint, whose config and plugins would be the fork's own code; TypeScript, Semgrep and Theme Check still run.
More in Merge checks.