[ci-drift] molecule-ai/molecule-core/staging: required-checks divergence detected #798

Closed
opened 2026-05-13 05:23:23 +00:00 by mc-drift-bot · 1 comment
Owner

Mc#800: REQUIRED_CHECKS in audit-force-merge.yml updated to match branch protection contexts (CI/all-required + sop-checklist). Both findings F3a+F3b resolved. Closing.

Mc#800: REQUIRED_CHECKS in audit-force-merge.yml updated to match branch protection contexts (CI/all-required + sop-checklist). Both findings F3a+F3b resolved. Closing.
mc-drift-bot added the tier:high label 2026-05-13 05:23:31 +00:00
Member

Triage — ci-drift findings, tier:high confirmed

Drift in audit-force-merge.yml REQUIRED_CHECKS env vs branch protection status_check_contexts on staging.

Gates:

  • G1 (existence): CONFIRMED — audit-force-merge script would flag non-force-merges as force
  • G2 (fix needed): Yes — REQUIRED_CHECKS env must match branch protection contexts
  • G3 (fix PR): None open yet

Core-DevOps: investigate drift between audit-force-merge.yml REQUIRED_CHECKS and branch protection contexts for staging. Issues tracked in RFC internal#219 §4 + §6.

## Triage — ci-drift findings, tier:high confirmed Drift in `audit-force-merge.yml` REQUIRED_CHECKS env vs branch protection status_check_contexts on staging. **Gates:** - G1 (existence): CONFIRMED — audit-force-merge script would flag non-force-merges as force - G2 (fix needed): Yes — REQUIRED_CHECKS env must match branch protection contexts - G3 (fix PR): None open yet Core-DevOps: investigate drift between audit-force-merge.yml REQUIRED_CHECKS and branch protection contexts for staging. Issues tracked in RFC internal#219 §4 + §6.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#798