Repository navigation
CI: consolidate the three Jules workflows into one #287
Description
This repo has three Jules workflows: jules.yml, jules-daily-codebase-ideation.yml (cron 06:00 UTC) and jules-daily-flake-sync.yml (cron 05:00 UTC). Each carries its own triggers, pins and setup, and fixes (like the jules-action @v1 pin) have to be applied file by file and repo by repo.
Consolidate into a single jules.yml: one on: block with both cron schedules, jobs gated on github.event.schedule, plus the existing workflow_dispatch and event-driven jobs. Honest expectation: per-run cost today is ~6 seconds, so the minute savings are small — the win is one file to pin, audit and fix, and one place where Jules quota (free tier: 15 tasks/day, 3 concurrent) is managed.
Acceptance: one Jules workflow file remains; both daily jobs still run at their current times; dispatch inputs preserved.
Acceptance criteria
- Exactly one Jules workflow file remains (
jules.yml);jules-daily-codebase-ideation.ymlandjules-daily-flake-sync.ymlare removed. - Both daily jobs still run at their current times (05:00 and 06:00 UTC), gated on
github.event.schedule. - Existing
workflow_dispatchinputs and event-driven jobs are preserved. - The jules-action pin and Jules quota management live in exactly one place.
Activity
dezren39 commentedon Oct 26, 2026
Intake review
🤖 Agent note · filed
Still live (verified this run): all three Jules workflows still exist on main —
.github/workflows/currently listsjules.yml,jules-daily-codebase-ideation.yml, andjules-daily-flake-sync.yml. No merged PR consolidates them.Related: the recurring Jules-review runs in the fleet log (the workflows' output is actively consumed), dezren39/nix and the other fleet repos carry their own Jules workflow copies — this issue is scoped to this repo only; do not cross-file per-repo copies of the same change.
Notes / risks: low risk and mostly mechanical, but the two daily crons (05:00 / 06:00 UTC) must survive the merge exactly — a schedule typo would silently stop a daily job, and the failure would only show as absence. The body's own framing stands: the win is one file to pin/audit, not minutes.
Suggested approach: fold both daily jobs into
jules.ymlgated ongithub.event.schedule, keepworkflow_dispatchinputs identical, and verify the merged file with a YAML parse plus a dispatch run of each gated job before deleting the two daily files.dezren39 commentedon Oct 28, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 28, 2026
🤖 Agent note · done
35726e8e9d(2026-10-28T18:50Z, viagh apicontents at HEAD): all three Jules workflow files still exist in.github/workflows/—jules.yml(cron0 4 * * 1weekly + issues + workflow_dispatch, 4× jules-action uses),jules-daily-codebase-ideation.yml(cron0 6 * * *),jules-daily-flake-sync.yml(cron0 5 * * *); every use pinsgoogle-labs-code/jules-action@bff7875eaa123cac6742b7cfc51005b95ba4d566 # v1.0.0, so the pin/audit duplication the issue describes is real. Note the weekly job in jules.yml is an extra schedule the consolidation must preserve alongside the two daily crons.repo-health:v1:fix:developing-today/code:issue:287): merge the two daily jobs into jules.yml gated ongithub.event.schedule, oneon:block with all three crons + issues + union of dispatch inputs, delete the two daily files, pin unchanged.hidden_files/packet-287-fix.json(goal workspace)1 remaining item
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
issue-closed); the workflows have since been migrated off Jules entirely, so this pass re-checks the premise before re-routing anything.dezren39 commentedon Nov 1, 2026
🤖 Agent note · done
Verdict — the problem this issue files no longer exists. The Jules era ended; all three workflows were migrated to pm-dispatch, and the duplication the issue complains about is gone.
Verified fresh 2026-11-01 at origin/main
9be9c2298c51(full reads of all three files viagh api):jules.ymlis nowname: pm-dispatch— the dispatch hub. Its header states it "was previously backed by the Jules service; it now uses the reusable pm-dispatch starter action". Every dispatch step uses the local reusable actiondeveloping-today/code/.github/actions/pm-dispatch-start@main. Zerojules-actionuses. The filename stays only becausemain-broken.ymlandrepo-sweeper.ymlreference that path.jules-daily-codebase-ideation.yml(cron0 6 * * *) andjules-daily-flake-sync.yml(cron0 5 * * *): both now launch OpenCode sessions via the samepm-dispatch-start@mainaction. Zerojules-actionuses in either.jules-actionpin to apply file by file (there is no external pin at all — one local action, referenced from one place in each file), and there is no Jules quota to manage (15 tasks/day free tier) because Jules is no longer invoked anywhere.History, for the record: triage task 2061 (2026-10-28) confirmed the issue as filed — at that date all three files really did pin
google-labs-code/jules-action@bff7875…— and routed fix task 2381. That task was cancelled 2026-10-30 (issue-closed), and the pm-dispatch migration then removed the premise entirely.What is NOT claimed: the literal acceptance "exactly one workflow file remains" was not performed. The two daily files still exist as separate small files; what they duplicate now is ~15 lines of identical concurrency/permissions/checkout boilerplate around a single shared local action — a different, much smaller concern than the one filed, and merging them into
jules.ymlwould change that file's trigger surface (it is path-referenced by two other workflows, and its header records the #304 concurrency lesson) for no pin/quota benefit. If a single-file layout is still wanted on pm-dispatch-era grounds, that is a new, smaller issue with its own scope — this one is closed as superseded rather than kept open on a premise that died.Closing as superseded by the pm-dispatch migration.