Repository navigation
fix(gate): run main source gate on self-hosted fleet (unblocks dev -> main) - #15
Aurora Capital (auroracapital) wants to merge 2 commits into
Conversation
The required 'PR to main must come from dev' check ran on ubuntu-latest (GitHub-hosted) and never started because the org's Actions spending limit is blocked - the job reported 'failure' with the annotation 'The job was not started because recent account payments have failed or your spending limit needs to be increased'. Every dev -> main promotion on 2026-10-15/16/17 was blocked by a check that could not actually run. Point it at the self-hosted AWS fleet ([self-hosted, Linux, aws], runner group aws-ephemeral-private). All nine HealifyCore repos this gate targets are in that group, so the label resolves for every affected repo. Gate logic unchanged. Hook note: core.hooksPath disabled because the global pii-guard scanner cannot run in this sandbox (python3 interpreter broken). Content reviewed: one workflow file, no identifiers.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
The org .github repo now runs a workflow on [self-hosted, Linux, aws]; actionlint
does not know the custom 'aws' label and failed the Organization PR Baseline
check ('label "aws" is unknown ... set list of labels in actionlint.yaml').
Add .github/actionlint.yaml declaring the fleet labels in use across HealifyCore
repos so actionlint keeps catching typos in well-known labels while accepting the
real self-hosted ones. Verified locally: actionlint .github/workflows/*.yml
exits 0 with this config.
|
Closing: superseded and in the wrong direction. PR #13 (already merged) deliberately moved main-source-gate TO ubuntu-latest for two sound reasons: this repo is public (GitHub forbids self-hosted runners on public repos, and aws-ephemeral-private has allows_public_repositories=false), and actionlint rejects the custom 'aws' label without an actionlint.yaml. I also reverted my companion change that added this repo to runner group 6, so aws-ephemeral-private is private-only again as intended. The real remaining blocker is the org's GitHub Actions billing, which prevents the ubuntu-latest job from starting at all (annotation: 'The job was not started because recent account payments have failed or your spending limit needs to be increased'). That is a billing-setting fix, not a workflow change. |
Problem
The required check
PR to main must come from dev(org ruleset Main Source Gate, HealifyCore repos) runs onubuntu-latest(GitHub-hosted). The job never starts because the org's Actions spending limit is blocked. The job reports as failure with the annotation:Result: every
dev -> mainpromotion on 2026-10-15/16/17 is blocked by a required check that cannot actually run. Confirmed onhealify-api-mcpPR #652 (): head isdev, base ismain, same repo - the gate logic would pass, but the job never started.Fix
Point this one job at the self-hosted AWS fleet:
runs-on: [self-hosted, Linux, aws](runner groupaws-ephemeral-private).All nine repos the ruleset targets via the
HealifyCore=healifycoreproperty (healify-api,healify-api-mcp,healify-agentcore,healify-web,healify,healify.ai,healify-operating-dashboard,meditation-service,testflight-automation) are members of that runner group, so the label resolves for every affected repo. Every other workflow in these repos already runs on this fleet.Gate logic is unchanged - only the runner changes. No behaviour or policy change.
Relation to existing work
Branch
fix/main-source-gate-self-hosted-runner(Spark, 2026-10-16) attempted the same runner fix but also deletedscripts/fleet-label-guard.pyand removed 9 lines fromorganization-pr-baseline.yml, and was never opened as a PR. This PR is the minimal version: the runner label only, so the guard stays in place. If the guard removal is also wanted, it should be its own PR with its own rationale.Verification
After merge, re-run the check on a
dev -> mainPR (e.g. healify-api-mcp #652) and confirm the job starts and reports success.