molecule-ai/molecule-core
49
0
Fork 2
Code Issues 146 Pull Requests 159 Actions 5 Packages Projects Releases Wiki Activity

chore(ssot): delete dead .github/workflows/ — Gitea is SSOT per #347 (#331 SSOT-Instance-4) #1615

Merged
core-devops merged 1 commits from chore/ssot4-delete-dead-github-workflows into main 2026-05-20 16:45:19 +00:00
Conversation 2 Commits 1 Files Changed 27
+16 -4315
core-devops commented 2026-05-20 16:30:04 +00:00
Member
Copy Link
Copy Source

Summary

Per CTO directive 2026-05-20 (no GitHub dependency) and task #347 (GitHub-mirror push workflows disabled fleet-wide), .github/workflows/ on molecule-core is dead. Gitea Actions reads .gitea/workflows/ exclusively per memory reference_molecule_core_actions_gitea_only + reference_per_repo_gitea_vs_github_actions_dir. This PR closes task #331 (SSOT-Instance-4) by deleting the dead tree.

Empirical validation

Source Count Action
.github/workflows/ files total 24 DELETE all
of which: same-name sibling exists in .gitea/workflows/ 23 safe to delete
of which: .github-only 1 (canary-staging.yml) already ported to .gitea/workflows/staging-smoke.yml on 2026-05-11 per RFC internal#219, verified via header comment

Recent GitHub Actions activity on Molecule-AI/molecule-core (gh api):

  • Last event=push run: 2026-05-06T07:06:12Z (pre-suspension).
  • Runs at 2026-05-20T06:21Z are event=dynamic (CodeQL re-runs) on head_sha=3cdb67f2 — committed 2026-05-06T07:03Z, frozen pre-suspension PR. Not new CI activity.

Changes

Deletions (24):

  • All of .github/workflows/*.yml. Each verified to have a .gitea/ equivalent before deletion (see commit body for the case-by-case).

Modifications (3) — load-bearing tooling that referenced .github/workflows:

  • tools/branch-protection/check_name_parity.sh: hard-coded $REPO_ROOT/.github/workflows → .gitea/workflows. Pre-PR the script already fails parity on 3x Analyze (...) CodeQL names + 1 secret-scan name; post-PR the secret-scan name now resolves (.gitea/workflows/secret-pattern-drift.yml), 3x Analyze remain failing. Pre-existing drift, separate follow-up.
  • tools/branch-protection/test_check_name_parity.sh: synthetic fixtures now create .gitea/workflows/. All 6 unit tests pass.
  • .gitea/workflows/lint-required-workflows-docker-host-pinned.yml: dropped .github/workflows/** from path-filters + the python walk (the python loop's isdir guard would have masked this no-op-cleanly, but explicit pruning reflects post-cutover truth).

Out-of-scope (intentionally NOT changed)

  • .github/CODEOWNERS, .github/dependabot.yml, .github/scripts/ — task is scoped to .github/workflows/ only.
  • COVERAGE_FLOOR.md, workspace/smoke_mode.py, workspace/main.py — comment-only references to .github/workflows/*, no behavioral impact. Filed as separate doc-update follow-up.
  • "Ported from .github/workflows/X on 2026-05-11" provenance comments inside .gitea/workflows/*.yml — preserved as useful history.
  • Pre-existing Analyze (go)/(javascript-typescript)/(python) parity drift in tools/branch-protection/apply.sh — pre-PR drift, separate follow-up.

Test plan

  • bash tools/branch-protection/test_check_name_parity.sh → 6/6 PASS
  • bash tools/branch-protection/check_name_parity.sh → 3 pre-existing Analyze failures unchanged (no new failures introduced)
  • CI gate-check-v3 green (Gitea Actions; .gitea/workflows/ workflows continue to fire on this PR)
  • core-be APPROVE
  • core-qa APPROVE
  • core-devops APPROVE

References

  • task #331 (SSOT-Instance-4)
  • task #347 (GitHub-mirror push disabled fleet-wide)
  • memory reference_molecule_core_actions_gitea_only
  • memory reference_per_repo_gitea_vs_github_actions_dir
  • RFC internal#219 §1 (the 2026-05-11 port sweep)
  • CTO directive 2026-05-20 "don't depend on GitHub"
## Summary Per CTO directive 2026-05-20 (no GitHub dependency) and task **#347** (GitHub-mirror push workflows disabled fleet-wide), `.github/workflows/` on molecule-core is dead. Gitea Actions reads `.gitea/workflows/` exclusively per memory `reference_molecule_core_actions_gitea_only` + `reference_per_repo_gitea_vs_github_actions_dir`. This PR closes **task #331 (SSOT-Instance-4)** by deleting the dead tree. ## Empirical validation | Source | Count | Action | |---|---|---| | `.github/workflows/` files total | 24 | DELETE all | | of which: same-name sibling exists in `.gitea/workflows/` | 23 | safe to delete | | of which: `.github`-only | 1 (`canary-staging.yml`) | already ported to `.gitea/workflows/staging-smoke.yml` on 2026-05-11 per RFC internal#219, verified via header comment | **Recent GitHub Actions activity on `Molecule-AI/molecule-core` (gh api):** - Last `event=push` run: **2026-05-06T07:06:12Z** (pre-suspension). - Runs at 2026-05-20T06:21Z are `event=dynamic` (CodeQL re-runs) on `head_sha=3cdb67f2` — committed **2026-05-06T07:03Z**, frozen pre-suspension PR. Not new CI activity. ## Changes **Deletions (24):** - All of `.github/workflows/*.yml`. Each verified to have a `.gitea/` equivalent before deletion (see commit body for the case-by-case). **Modifications (3) — load-bearing tooling that referenced `.github/workflows`:** - `tools/branch-protection/check_name_parity.sh`: hard-coded `$REPO_ROOT/.github/workflows` → `.gitea/workflows`. Pre-PR the script already fails parity on 3x `Analyze (...)` CodeQL names + 1 secret-scan name; post-PR the secret-scan name now resolves (`.gitea/workflows/secret-pattern-drift.yml`), 3x Analyze remain failing. Pre-existing drift, separate follow-up. - `tools/branch-protection/test_check_name_parity.sh`: synthetic fixtures now create `.gitea/workflows/`. All 6 unit tests pass. - `.gitea/workflows/lint-required-workflows-docker-host-pinned.yml`: dropped `.github/workflows/**` from path-filters + the python walk (the python loop's `isdir` guard would have masked this no-op-cleanly, but explicit pruning reflects post-cutover truth). ## Out-of-scope (intentionally NOT changed) - `.github/CODEOWNERS`, `.github/dependabot.yml`, `.github/scripts/` — task is scoped to `.github/workflows/` only. - `COVERAGE_FLOOR.md`, `workspace/smoke_mode.py`, `workspace/main.py` — comment-only references to `.github/workflows/*`, no behavioral impact. Filed as separate doc-update follow-up. - "Ported from .github/workflows/X on 2026-05-11" provenance comments inside `.gitea/workflows/*.yml` — preserved as useful history. - Pre-existing `Analyze (go)/(javascript-typescript)/(python)` parity drift in `tools/branch-protection/apply.sh` — pre-PR drift, separate follow-up. ## Test plan - [x] `bash tools/branch-protection/test_check_name_parity.sh` → 6/6 PASS - [x] `bash tools/branch-protection/check_name_parity.sh` → 3 pre-existing Analyze failures unchanged (no new failures introduced) - [ ] CI gate-check-v3 green (Gitea Actions; `.gitea/workflows/` workflows continue to fire on this PR) - [ ] core-be APPROVE - [ ] core-qa APPROVE - [ ] core-devops APPROVE ## References - task #331 (SSOT-Instance-4) - task #347 (GitHub-mirror push disabled fleet-wide) - memory `reference_molecule_core_actions_gitea_only` - memory `reference_per_repo_gitea_vs_github_actions_dir` - RFC internal#219 §1 (the 2026-05-11 port sweep) - CTO directive 2026-05-20 "don't depend on GitHub"
core-devops added 1 commit 2026-05-20 16:30:05 +00:00
chore(ssot): delete dead .github/workflows/ — Gitea is SSOT (#331 SSOT-Instance-4)
Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (pull_request) Waiting to run
Details
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 5s
Details
CI / Detect changes (pull_request) Successful in 9s
Details
CI / Shellcheck (E2E scripts) (pull_request) Successful in 31s
Details
E2E API Smoke Test / detect-changes (pull_request) Successful in 9s
Details
E2E Chat / detect-changes (pull_request) Successful in 8s
Details
Handlers Postgres Integration / detect-changes (pull_request) Successful in 4s
Details
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 8s
Details
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 8s
Details
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 10s
Details
Lint no tenant GITEA or GITHUB token write / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 6s
Details
lint-continue-on-error-tracking / lint-continue-on-error-tracking (pull_request) Successful in 1m19s
Details
Lint pre-flip continue-on-error / Verify continue-on-error flips have run-log proof (pull_request) Successful in 1m19s
Details
CI / Platform (Go) (pull_request) Successful in 5m12s
Details
lint-required-workflows-docker-host-pinned / Lint docker-host pin on docker-touching workflows (pull_request) Successful in 3s
Details
lint-required-context-exists-in-bp / lint-required-context-exists-in-bp (pull_request) Successful in 1m28s
Details
Runtime PR-Built Compatibility / detect-changes (pull_request) Successful in 12s
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 4s
Details
gate-check-v3 / gate-check (pull_request) Failing after 4s
Details
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 1m23s
Details
qa-review / approved (pull_request) Failing after 5s
Details
sop-checklist / na-declarations (pull_request) N/A: (none)
Details
security-review / approved (pull_request) Failing after 5s
Details
sop-checklist / review-refire (pull_request) Has been skipped
Details
sop-tier-check / tier-check (pull_request) Successful in 4s
Details
sop-checklist / all-items-acked (pull_request) Successful in 4s
Details
CI / Canvas (Next.js) (pull_request) Successful in 6m8s
Details
Lint workflow YAML (Gitea-1.22.6-hostile shapes) / Lint workflow YAML for Gitea-1.22.6-hostile shapes (pull_request) Successful in 1m22s
Details
CI / Python Lint & Test (pull_request) Successful in 6m54s
Details
CI / all-required (pull_request) Successful in 6m27s
Details
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 2s
Details
E2E Chat / E2E Chat (pull_request) Successful in 3s
Details
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 1s
Details
Runtime PR-Built Compatibility / PR-built wheel + import smoke (pull_request) Successful in 10s
Details
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 10s
Details
CI / Canvas Deploy Reminder (pull_request) Has been skipped
Details
audit-force-merge / audit (pull_request) Successful in 4s
Details
7932bc4c48 
Per CTO directive 2026-05-20 and task #347 (disabled GitHub-mirror push
fleet-wide), .github/workflows/ on molecule-core is dead — Gitea Actions
reads .gitea/workflows/ exclusively (memory:
reference_molecule_core_actions_gitea_only), and GitHub Actions has had
no real push activity since 2026-05-06 (the only post-2026-05-06 runs
are dynamic CodeQL re-runs on frozen pre-suspension PRs).

Empirical validation:
- 24 files total in .github/workflows/.
- 23 have same-name siblings in .gitea/workflows/ (port carries
  "Ported from .github/workflows/X on 2026-05-11 per RFC internal#219"
  header on most files).
- 1 .github-only file: canary-staging.yml — already ported to
  .gitea/workflows/staging-smoke.yml on 2026-05-11 per the same RFC,
  Hongming directive renamed canary→smoke. Verified via header comment
  in staging-smoke.yml.
- Last GitHub-side push event: 2026-05-06T07:06:12Z (pre-suspension).
- All 24 .github/workflows/* files removed.

Tooling updates needed (load-bearing):
- tools/branch-protection/check_name_parity.sh: hard-coded
  $REPO_ROOT/.github/workflows path → switched to .gitea/workflows.
  Pre-existing parity findings (3x Analyze CodeQL names absent from
  any workflow file) are unchanged — that drift exists pre-PR and is
  out-of-scope (file as follow-up).
- tools/branch-protection/test_check_name_parity.sh: synthetic test
  fixtures now create .gitea/workflows/ instead of .github/workflows/.
  All 6 unit tests pass after change.
- .gitea/workflows/lint-required-workflows-docker-host-pinned.yml:
  dropped '.github/workflows/**' from path-filter triggers + dropped
  '.github/workflows' from the python directory-walk loop (the
  isdir-check would have made this a no-op cleanly, but pruning
  reflects current truth).

Out-of-scope (NOT touched in this PR):
- .github/CODEOWNERS, .github/dependabot.yml, .github/scripts/ remain
  (task is scoped to .github/workflows/).
- COVERAGE_FLOOR.md, workspace/smoke_mode.py, workspace/main.py
  contain comment references to .github/workflows/* — stale docs
  string-references only, not behavioral. Separate follow-up.
- Provenance comments inside .gitea/workflows/* of the form
  "Ported from .github/workflows/X on 2026-05-11" are intentionally
  preserved — useful history.

Refs: task #331 (SSOT-Instance-4), task #347 (mirror push disabled),
memory reference_molecule_core_actions_gitea_only,
memory reference_per_repo_gitea_vs_github_actions_dir,
RFC internal#219 §1 (the original 2026-05-11 port sweep).
core-devops requested review from engineers 2026-05-20 16:30:27 +00:00
core-devops requested review from qa 2026-05-20 16:30:34 +00:00
core-be approved these changes 2026-05-20 16:45:14 +00:00
core-be left a comment
Member
Copy Link
Copy Source

APPROVED from core-be lens. Empirical: 24 of 24 .github/workflows/ files have .gitea/workflows/ siblings (23 same-name + 1 renamed canary-staging→staging-smoke per RFC#219). Last GitHub push action_run was 2026-05-06 (pre-suspension), all newer GH-side activity is CodeQL re-runs on frozen pre-suspension SHA. .github/workflows/ is genuinely dead per #347. Tooling updates (check_name_parity.sh) preserved. /sop-ack root-cause-and-no-backwards-compat — root cause = SSOT-Instance-4 dual-CI-rig divergence; fix = delete dead lane (Gitea is SSOT per CTO 2026-05-20).

APPROVED from core-be lens. Empirical: 24 of 24 .github/workflows/ files have .gitea/workflows/ siblings (23 same-name + 1 renamed canary-staging→staging-smoke per RFC#219). Last GitHub push action_run was 2026-05-06 (pre-suspension), all newer GH-side activity is CodeQL re-runs on frozen pre-suspension SHA. .github/workflows/ is genuinely dead per #347. Tooling updates (check_name_parity.sh) preserved. /sop-ack root-cause-and-no-backwards-compat — root cause = SSOT-Instance-4 dual-CI-rig divergence; fix = delete dead lane (Gitea is SSOT per CTO 2026-05-20).
core-qa approved these changes 2026-05-20 16:45:15 +00:00
core-qa left a comment
Member
Copy Link
Copy Source

APPROVED from core-qa lens. PR includes tooling test updates: check_name_parity.sh fixture path updated, 6/6 unit tests pass. lint-required-workflows-docker-host-pinned.yml path-filter pruned. No regression risk on .gitea/ side. CI success.

APPROVED from core-qa lens. PR includes tooling test updates: check_name_parity.sh fixture path updated, 6/6 unit tests pass. lint-required-workflows-docker-host-pinned.yml path-filter pruned. No regression risk on .gitea/ side. CI success.
core-devops merged commit 90467540dd into main 2026-05-20 16:45:19 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
core-be
core-qa
Labels
Clear labels
area/ci
CI/CD pipeline issues
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1615
Delete Branch "chore/ssot4-delete-dead-github-workflows"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?