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
source-control: dossier branches per owning item - part 2 of 2 #10150
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
A decision is recorded on this issue, and it settles the four open design questions from the earlier lane stop. They were where the step runs, which scanner it uses, what it scans, and what "machine data" covers.
Decision recorded. The Issue Triage session settled the design question from the lane stop of 2026-11-01 using the repository's existing patterns. The answer changes neither the intent of #7579 nor its primary design, so this issue does not need the owner. This comment amends the issue body, which stays as split.
[quote truncated; the full decision is at https://github.com//issues/10150#issuecomment-6559809936]
The decision settles every open question, so nothing further is asked. As I read it, the work adds a guardrails pre-push-content entry, a contract test for it, and the README and changelog updates. It doesn't depend on #10149 at run time.
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41282312537, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-01T07:31:44Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41320295232, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-01T15:24:16Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.
Activity
github-actions commentedon Oct 26, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
A decision is recorded on this issue, and it settles the four open design questions from the earlier lane stop. They were where the step runs, which scanner it uses, what it scans, and what "machine data" covers.
The decision settles every open question, so nothing further is asked. As I read it, the work adds a guardrails
pre-push-contententry, a contract test for it, and the README and changelog updates. It doesn't depend on #10149 at run time.Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 26, 2026
Not admitted to the issue lane yet: blocker #7578 is not closed by a listed human or a merge.
melodic-automation-lanes commentedon Nov 1, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41282312537, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-01T07:31:44Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.6 remaining items
github-actions commentedon Nov 1, 2026
melodic-automation-lanes commentedon Nov 1, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41320295232, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-01T15:24:16Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 1, 2026
github-actions commentedon Nov 1, 2026