Skip to content

docs/handbook.html: stop every README PR rewriting the handbook's README blob and line cap, so open README PRs stop conflicting with each other #519

Closed

Description

@brettheap

First of v1.1.0's README work. Every README-touching PR regenerates the handbook's footer clause and README blob (tests/test_repo_hygiene.py), so any two open README PRs conflict, and they land one at a time, about two hours apart. Fixing this makes every later README PR cheap. GitHub's merge queue (#461) waits for it too.

From the v1.1.0 triage of the v1.0.0 known limits on #461. One pull request covers the lines below.

Lines

  • Every README PR rewrites the handbook's README blob (and the line cap), so open README PRs conflict pairwise. Where: docs/handbook.html:1885; tests/test_repo_hygiene.py:1186, :1787-1795. Effort M; CI (all three). On main 3121945: CI cost: the handbook must name README.md blob ae817c5… exactly once and equal to README's blob (:1787-1795), and README is 1422 lines against a 1422 cap (:1186), so every README PR edits the same two lines.

Activity

  1. added this to the v1.1.0 milestone on Oct 14, 2026
  2. brettheap commented on Oct 14, 2026

    @brettheap
    ContributorAuthor

    CLAIMED — lane openRepoShape-3, session b30e8b49-f249-4668-adb1-1dbfa93c09e1@Eagle, 2026-10-14T15:19:35Z, for #519

    Logged in lanes/log/openRepoShape-3.md at d6981248a0932e544dc0640146c191f9f8baad9a.

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

    1. existing `CLAIMED —` comments on opensoft/openRepoShape#519:
       none
    2. `gh pr list --repo opensoft/openRepoShape --state all --search "#519"`, kept where the row or its body names `#519`:
       none
    3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `519` as a whole token:
       none
    
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