Commit graph

4 commits

Author SHA1 Message Date
cschlaefke
ffa264f827 docs(adr): accept no-approval rule for fork PR runs (ADR-0003)
Some checks failed
CI / flutter (pull_request) Successful in 1m23s
CI / web-build (pull_request) Successful in 1m16s
CI / supabase (pull_request) Successful in 9s
CI / supabase-tests (pull_request) Successful in 33s
CI / e2e (pull_request) Failing after 5m50s
Refs #43

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-04 01:06:55 +01:00
cschlaefke
25610c1ec9 docs(ci): correct guard rationale and unverified claims in ADR-0003
Refs #43

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-03 13:58:09 +01:00
cschlaefke
501310f43b docs(ci): verify fork-PR approval logic and correct runner advice in ADR-0003
Refs #43

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-03 13:51:46 +01:00
cschlaefke
666ba64fcc fix(ci): document fork-PR risk for docker-host runner and guard supabase-tests
Add ADR-0003 with Forgejo 8.0.3 options and a step-by-step guide for
runner/Forgejo settings, correct the misleading guard comments in ci.yml
and apply the comfort guard to supabase-tests too.

Refs #43

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-03 13:50:25 +01:00