Repository navigation
Conversation
Signatures live in the shared repository config, so signing in one worktree invalidates every other worktree whose configuration or hooks differ. When extensions.worktreeConfig is enabled, read and write them with `git config --worktree` instead; without the extension `--worktree` fails in a repo with linked worktrees, so `--local` remains the default. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wo4FerFK9aaxrGrmVE9ncZ
ubuntu-latest now resolves to ubuntu-26.04, for which setup-ruby has
no Ruby 2.6-3.1 builds ("Unavailable version 3.0.7 for ruby on
ubuntu-26.04"), so those matrix entries fail before running specs.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wo4FerFK9aaxrGrmVE9ncZ
Name ubuntu-26.04 explicitly so runners do not move when ubuntu-latest does. setup-ruby has no Ruby 2.6-3.1 builds for ubuntu-26.04, so a matrix include keeps those rows on ubuntu-24.04. Non-ubuntu rows still use <os>-latest. The explicit job name keeps check names as "rspec (<ruby>, <os>)", which upstream requires. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wo4FerFK9aaxrGrmVE9ncZ
Merge pin-ci-runner-to-ubuntu-24.04 (sds#902) so the rspec checks for Ruby 2.6 through 3.1 run on ubuntu-24.04, where setup-ruby still has those versions. This merge drops out once sds#902 lands upstream. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wo4FerFK9aaxrGrmVE9ncZ
Owner
Author
|
Claude: Moved upstream to sds#903 |
Coverage Report for CI Build 39672806112Coverage at 92.027% (no base build to compare)Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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.
Claude: This PR was written by Claude Code on behalf of @apiology.
Problem
Signing in one git worktree breaks commits in the others:
Anyone whose worktrees carry different
.overcommit.ymlfiles or hook plugins (e.g. branches that change the config) has to re-sign on every switch.Solution
When
extensions.worktreeConfigis enabled, signatures and the recordedverify_signatureschoice are read and written withgit config --worktreeinstead of--local, so each worktree keeps its own; without the extension--worktreefails in a repo with linked worktrees (fatal: --worktree cannot be used with multiple working trees unless the config extension worktreeConfig is enabled), so behaviour there is unchanged.