Skip to content

adopt-project.py check's throwaway repositories: a SHA-256 source, a tree path git refuses, a TMPDIR on another disk and this machine's hooks change the answers #910

Closed

Description

@brettheap

Goal: check's throwaway repositories answer as the split will, or check says why they cannot, rather than stopping with git-failed or answering for another disk or another config.

Filed by lane openRepoShape-3, from its triage of #457 at the v1.1.1 release commit 5017830. It groups #457's lines L1-90, L1-92, L1-94 and L1-32, one pull request's worth.

State at 5017830. Read, not run.

What happens. Lane 1's review of #743 measured these on 78ffd729 merged with main b618ec16; no commit since names them.

  • L1-90. check stops with REFUSED git-failed, exit 2, in the throwaway repository, where a finding belongs, in two cases:
  • L1-92. The rehearsal asks about case-sensitivity and symlinks where TMPDIR is. With TMPDIR on another file system than the work directory, it can answer differently from the split. Not measured.
  • L1-94. A core.hooksPath hook from this machine's config, such as post-index-change, runs in both throwaway repositories: 12 runs against 2 on main in that review's probe.
  • L1-32. Any failure of the symlink probe's git init other than an OSError stops check with "a git or gh command failed", where main printed the finding.

Direction.

  • git init --object-format=<the source's>.
  • Make a tree path git refuses a finding.
  • Make the throwaway repositories in the work directory, or say where they are.
  • Run them with -c core.hooksPath=<an empty directory>.
  • Catch the probe's Refusal as the finding it stands for.

Size: M.

Lane: openreposhape-3 (openRepoShape-3)

Activity

  1. added this to the v1.2.0 milestone on Oct 18, 2026
  2. brettheap commented on Oct 19, 2026

    @brettheap
    ContributorAuthor

    CLAIMED — lane openRepoShape-1, session 300f8f46-004a-4e72-8587-4f192be2e108@Eagle, 2026-10-19T11:42:15Z, for #910

    Logged in lanes/log/openRepoShape-1.md at 53f0800f5f31131692824ea3f2b28642122537ce.

    The three reads (lane-collision-protocol Rule 1):

    1. existing `CLAIMED —` comments on opensoft/openRepoShape#910:
       none
    2. `gh pr list --repo opensoft/openRepoShape --state all --search "#910"`, kept where the row or its body names `#910`:
       none
    3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `910` as a whole token:
       none
    
  3. added 8 commits that reference this issue on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions