Skip to content

ci: merge ready pull requests on a schedule, not when a laptop is awake - #4279

Merged
gHashTag merged 1 commit into
masterfrom
ci/merge-ready-prs-on-a-schedule
Sep 19, 2026
Merged

gHashTag merged 1 commit into
masterfrom
ci/merge-ready-prs-on-a-schedule

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #4278

The local scheduled merge has failed on every run since 2026-09-17 07:39 UTC (the session model), silently. Auto Merge Ready PRs already exists and does the same job; it now runs every 20 minutes with a concurrency group. What it merges is unchanged.

🤖 Generated with Claude Code

The batch merge ran as a local scheduled task and every run since 2026-09-17
07:39 UTC failed in three seconds on the session model, invisibly: the script
logs when it runs and it never ran. Thirty-three bee pull requests sat open.

`Auto Merge Ready PRs` already does this job and was workflow_dispatch only.
It now runs every 20 minutes under a concurrency group, with no change to what
it merges - an issue reference and green checks.

The classification note that called auto-merge "disabled by policy" is also
corrected; pull requests have been landing through GitHub's auto-merge all week.

Closes #4278

Gates: the workflow parses and lists schedule + workflow_dispatch;
python3 scripts/ci/check_pr_branch_filters.py exits 0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-19 15:08:02 UTC

Summary

Status Count
Total Open PRs 39
PRs with Failing Checks 18
PRs with All Checks Green 21
READY 20
FAILING 18
PENDING 0
NO CHECKS YET 0

These columns do not partition: 20 + 18 + 0 + 0 = 38, and there are 39 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag enabled auto-merge (squash) September 19, 2026 15:08
@gHashTag
gHashTag merged commit 6ed2f04 into master Sep 19, 2026
26 of 29 checks passed
gHashTag added a commit that referenced this pull request Sep 20, 2026
… path (#4304)

Three checks are red on master. Two are this loop's.

CENSUS. tools/census/quiet.txt pinned `workflow files read 51`; the tree holds
57. The six added since the pin are #4277, #4279, #4281, #4283, #4291 and
#4300, all merged by this loop, and cli-tri has been red since 2026-09-17.
What moved, explicitly: quiet 51 -> 57 workflow files and 123 -> 135 "named a
path but not quiet"; shell 51 -> 57 files, 72 -> 78 jobs, 249 -> 267 run-steps,
228 -> 246 steps the runner runs with `bash -eo pipefail`. The gates did not
change; the population grew.

HOME PATH. feed_defects.py carries a comment explaining that an absolute
`/Users/<name>/t27/target/release/t27c` once went into 137 open issues -- and
spells it out to say so, which is what the scan catches. It now reads
`.../t27/target/release/t27c`, same meaning, no home directory.

WORKTREES. That gate also failed in every worktree on a path no commit
contains: it excludes the `.git` DIRECTORY, and a worktree's `.git` is a FILE
holding `gitdir: /Users/...`. `--exclude=.git` joins `--exclude-dir=.git`. The
reviewer measures in a detached worktree and every bee works in one.

NOT FIXED HERE: `coverage` reports 544 stale seals and has no successful run in
its last 60 on master, reaching back past 2026-09-18. Re-sealing 544 specs
records what the compiler now produces -- a decision about the ledger, not a
repair.

Closes #4303

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The batch merge lived on a laptop, and it has been failing silently since 2026-09-17

1 participant