You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Skip a YAML Block Scalar When the Prose Gate Reads a Compose File's Volume Entries #3694
Raised by the review of promotion #3693, on the change #3685 made.
container_paths in .github/actions/prose-gate/prose_lint.py decides which lines of a Compose file are a volume entry's container side by indentation alone. It does not know a YAML block scalar (| or >), so a volumes: key and a mount-shaped list item written inside one read as a real volume entry, and the home-path rule skips them.
In compose.yml this produces no finding. The same text in ledger.yml produces home-path. A x-note: | scalar inside a long-syntax volume entry holding - ./old:/home/zed/media is skipped the same way.
Reach is narrow: it needs mount-shaped text inside a block scalar in a Compose file, and it only hides text shaped exactly like a mount target. The smallest fix is to treat a key line ending in a block-scalar indicator as opening an opaque region, skipping every deeper-indented line until the indentation returns.
Claim released: feature/burndown-3684-3694 merged to develop as #3712 and its branch and worktree are cleaned up. Follow-ups: #3711, #3714. This issue closes when the next develop -> main promotion merges.
Activity
Promote Develop: Carry a New Verbatim Section, Read a Null GraphQL No…
ptr727 commentedon Oct 31, 2026
Backlog burndown round 3 claim. Branch:
feature/burndown-3684-3694. Group: #3684, #3694.Predicted file set:
.github/actions/prose-gate/prose_lint.py.github/actions/prose-gate/prose-gate.jsontests/test_prose_lint.pyNo other live group may edit these files until this branch merges or the claim is released here.
Read a Move Out of an Unread Source Whole and Skip a Compose Block Sc…
ptr727 commentedon Oct 31, 2026
Claim released:
feature/burndown-3684-3694merged todevelopas #3712 and its branch and worktree are cleaned up. Follow-ups: #3711, #3714. This issue closes when the nextdevelop->mainpromotion merges.