Mark/org_mode

decompose-on-issue-opened trigger fires on every issue — immediately exits, no Decompose: issues ever produced #11

New issue

Closed

opened 2026-05-24 23:03:10 +00:00 by Mark · 0 comments

Mark commented

2026-05-24 23:03:10 +00:00

Owner

The decompose trigger fires on every issues.opened event and runs decompose-executor.py, which checks if the issue title starts with "Decompose:". Nothing in the pipeline ever produces a Decompose: prefix issue, so the script immediately exits every time.

Real work: triage → label → fixer/quickfix/human. Decompose queue is an unused concept.

The decompose trigger fires on every issues.opened event and runs decompose-executor.py, which checks if the issue title starts with "Decompose:". Nothing in the pipeline ever produces a Decompose: prefix issue, so the script immediately exits every time. Real work: triage → label → fixer/quickfix/human. Decompose queue is an unused concept.

Mark added the

label

2026-05-24 23:04:41 +00:00

Mark referenced this issue from a commit

2026-05-25 02:58:48 +00:00

fix: block stale decompose triggers at creation time, remove decompose queue docs

Mark

2026-05-25 02:58:48 +00:00

closed this issue
added
triage-approved
and removed
quickfix
labels

Sign in to join this conversation.

No labels

blocked:needs-decision

needs-decompose

security/medium

triage-approved

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Mark/org_mode#11

No description provided.