From 9d49bc08c2f3c0f6760bcf511b89272e24825241 Mon Sep 17 00:00:00 2001
From: cayossarian <23534755+cayossarian@users.noreply.github.com>
Date: Sat, 22 Aug 2026 21:23:50 -0700
Subject: [PATCH] chore: drop the develop branch from CI triggers

The develop branch is deleted. It carried no commits that main did not
already have, everything ships from main through tags, and it was the one
branch no ruleset covered -- push, force-push and delete were all
unrestricted on it for every collaborator with write, silently, because
`protect_main` targets `~DEFAULT_BRANCH` and can never match anything
else.

That leaves the push and pull_request triggers naming a ref that cannot
exist, and a dispatch example telling a reader to run against it. Point
the example at main and note that a tag works too, which is the case
worth reaching for anyway -- checking what a release actually built.
---
 .github/workflows/ci.yml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 8647d9d..3728aee 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -2,14 +2,15 @@ name: CI
 
 on:
   push:
-    branches: [ main, develop ]
+    branches: [ main ]
   pull_request:
-    branches: [ main, develop ]
+    branches: [ main ]
   # Push and pull_request both arrive by webhook, so a dropped delivery leaves a
   # commit with no run at all -- which reads the same as a commit that passed.
-  # Dispatch re-runs this against any ref on demand.
+  # Dispatch re-runs this against any ref on demand -- a branch, or a tag when
+  # checking what a release actually built.
   #
-  #   gh workflow run ci.yml --ref develop
+  #   gh workflow run ci.yml --ref main
   workflow_dispatch:
 
 jobs: