Skip to content

ci(jules): watch only CI workflows, split concurrency group (#304) - #357

Merged
dezren39 merged 1 commit into
mainfrom
sweep/304-jules-workflow-run
Oct 19, 2026
Merged

dezren39 merged 1 commit into
mainfrom
sweep/304-jules-workflow-run

Conversation

@dezren39

@dezren39 dezren39 commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

Problem

jules.yml subscribed to every workflow completion (workflow_run: workflows: ["*"]), so every completion in the repo created a Jules run whose jobs all skipped. Fresh count this run: 53 of the last 100 repo runs are Jules, 48 of them skipped workflow_run no-ops (issue reported 54/44 on 2026-10-18).

Worse, the single workflow-level concurrency group (${{ github.workflow }}-${{ github.ref }}) is shared by all of them — for workflow_run events github.ref is the default branch — and GitHub's default queue: single semantics let a noise completion cancel a pending ci-failure-fix run, the one run the trigger exists for (same failure mode as #302).

Solution

  • workflow_run.workflows now lists only the CI workflows ci-failure-fix can act on: mcpx, mcpx conformance, mcpx nix build, nix ci, id (names verified against each workflow's name: on main).
  • branches-ignore: [main] on the workflow_run trigger: the job ignores main-branch failures, so main completions no longer create a run at all.
  • The workflow-level concurrency group is removed. Each job carries its own job-level group keyed by its target — weekly-cleanup, issue-<number>, ci-failure-fix-<workflow>-<branch>, manual — all with cancel-in-progress: false, so same-target supersede behaviour is kept and a run whose jobs all skip shares a group with nothing that would act.

Acceptance notes

  • Non-CI workflow completions create no Jules run; main-branch completions of watched workflows create none either.
  • GitHub offers no conclusion filter for workflow_run, so a successful non-main completion of a watched workflow still creates one inert skipped run — but it can no longer displace anything (no workflow-level group; its only job-level group is keyed to that workflow+branch's failure-fix target and the job is skipped).
  • schedule, issues: [labeled] and workflow_dispatch triggers are unchanged.

Verification

  • YAML parses; trigger, per-job groups and absence of a top-level group confirmed from the parsed document.
  • prettier --check .github/workflows/jules.yml passes (treefmt-clean).
  • Single-repo: no workflow_run: ["*"] subscription exists in developing-today/opencode, developing-today/openchamber or dezren39/nix.

Closes #304


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

)

workflow_run subscribed to every workflow completion ('*'), creating a
skipped no-op Jules run per completion (48 of the last 100 repo runs),
and the single workflow-level concurrency group (github.ref is the
default branch for workflow_run) let a noise run cancel a pending
ci-failure-fix run.

- workflow_run now lists only the CI workflows ci-failure-fix can act on
  (mcpx, mcpx conformance, mcpx nix build, nix ci, id) and ignores main
  completions, which the job would skip anyway.
- The workflow-level concurrency group is gone; each job carries its own
  group keyed by its target (issue number / triggering workflow+branch),
  so a run whose jobs all skip can never displace a run that would act.
@dezren39
dezren39 requested a review from a team as a code owner October 19, 2026 14:06
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-19T14:06:45.343843Z 55efb43 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@dezren39
dezren39 merged commit 238adf4 into main Oct 19, 2026
3 checks passed
@dezren39
dezren39 deleted the sweep/304-jules-workflow-run branch October 19, 2026 14:09
@coderabbitai

coderabbitai Bot commented Oct 19, 2026

Copy link
Copy Markdown

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8dc921a2-3f7a-4f0e-beb9-fddde914ec82
📥 Commits

Reviewing files that changed from the base of the PR and between 6bc9c3d and 55efb43.

📒 Files selected for processing: 1
  • .github/workflows/jules.yml
+------------------------------------------------+
| If this were a race, you'd still be importing. |
+------------------------------------------------+
  \
   \     /)/)
        ( '')
        /  |
      o(___)
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant