docs: Add RCC smoke test fix workflow documentation#2613
Merged
Conversation
Adds .claude/skills/rcc-smoke-fix.md — a slash-command skill (/rcc-smoke-fix) that implements the scheduled job: - Adds/refreshes a `krlmlr` remote (force-fetch, prune) to avoid stale cache - Batch-collects all *-dev remote-tracking branches + existing broken-* branches in a single git branch -r pass (no extra API calls) - For each *-dev branch (including broken-*-dev), iterates commits oldest-first since 2026-04-11 and checks the `rcc` commit-status context via gh api, stopping at the first `failure` and skipping if a broken-<branch>-<sha7> branch already exists - Creates the fix branch at the failing commit, fixes testthat::test_local() and R CMD check . (snapshots, R code, roxygen), commits the fix, then cherry-picks all remaining vendor commits from the *-dev branch - Pushes to krlmlr/rigraph with --force-with-lease https://claude.ai/code/session_01NMbDS1CNtybJEqfuzHgR3E
…ame) Branch name is broken-<sha7>-dev rather than broken-<branch>-<sha7> because the SHA already uniquely identifies the commit. https://claude.ai/code/session_01NMbDS1CNtybJEqfuzHgR3E
- Branch naming: broken-<sha40>-dev (full SHA, not sha7) - patch/ is allowed to be modified (sometimes necessary for C API changes) - Fix priority: patch/ > glue/Stimulus > R/ > snapshots > tests (last resort) - Update constraints section accordingly https://claude.ai/code/session_01NMbDS1CNtybJEqfuzHgR3E
Two bugs fixed in the skill: 1. Skip-on-existing-fix moved outside the status loop. Previously the break on finding a broken-*-dev branch fired *inside* the commit iteration, so a later already-fixed commit could short-circuit before reaching an earlier failure with no fix branch yet. Now we scan all commits for the true earliest failure first, then check existence. 2. Cherry-pick section updated for mixed vendor+fix commits. The *-dev branch may contain non-vendor fix commits alongside vendor commits (e.g. a glue-code repair pushed directly to the branch). These must be cherry-picked verbatim. Conflicts on non-vendor files are expected and must be resolved, not skipped. A final R CMD check after all cherry-picks is now required. https://claude.ai/code/session_01NMbDS1CNtybJEqfuzHgR3E
krlmlr
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds comprehensive documentation for a scheduled workflow that automatically detects and fixes failures in the
rcc(smoke test) commit status across development branches inkrlmlr/rigraph.The documentation outlines a multi-step process to:
*-devbranches for the earliest commit with a failingrccstatus since 2026-04-11broken-<sha>-devfix branches for failures without existing fixesKey Features
Test Plan
N/A — This is documentation only. No code changes or automated tests are involved.
https://claude.ai/code/session_01NMbDS1CNtybJEqfuzHgR3E