fix: duplicated label ID lookup — ensure_blocked_label_id vs _ilc_ensure_label_id #282

Closed
opened 2026-04-06 09:21:33 +00:00 by dev-bot · 0 comments
Collaborator

Problem

lib/ci-helpers.sh:13 defines ensure_blocked_label_id() with cache _BLOCKED_LABEL_ID.
lib/issue-lifecycle.sh:55 defines _ilc_ensure_label_id() with cache _ILC_LABEL_IDS.

Both create the 'blocked' label if missing. Both are sourced by dev-poll.sh, so the caches are independent and can cause duplicate API calls.

Fix

Remove ensure_blocked_label_id() from ci-helpers.sh. Update its callers to use _ilc_ensure_label_id from issue-lifecycle.sh (which is the more general implementation supporting any label name).

Affected files

  • lib/ci-helpers.sh (remove ensure_blocked_label_id)
  • Any callers of ensure_blocked_label_id (switch to _ilc_ensure_label_id)

Acceptance criteria

  • Only one label ID lookup function exists
  • No duplicate API calls for label creation
## Problem lib/ci-helpers.sh:13 defines ensure_blocked_label_id() with cache _BLOCKED_LABEL_ID. lib/issue-lifecycle.sh:55 defines _ilc_ensure_label_id() with cache _ILC_LABEL_IDS. Both create the 'blocked' label if missing. Both are sourced by dev-poll.sh, so the caches are independent and can cause duplicate API calls. ## Fix Remove ensure_blocked_label_id() from ci-helpers.sh. Update its callers to use _ilc_ensure_label_id from issue-lifecycle.sh (which is the more general implementation supporting any label name). ## Affected files - lib/ci-helpers.sh (remove ensure_blocked_label_id) - Any callers of ensure_blocked_label_id (switch to _ilc_ensure_label_id) ## Acceptance criteria - [ ] Only one label ID lookup function exists - [ ] No duplicate API calls for label creation
dev-bot added the
backlog
label 2026-04-06 09:21:33 +00:00
dev-bot self-assigned this 2026-04-06 10:04:05 +00:00
dev-bot added
in-progress
and removed
backlog
labels 2026-04-06 10:04:05 +00:00
dev-bot removed their assignment 2026-04-06 10:09:03 +00:00
dev-bot removed the
in-progress
label 2026-04-06 10:09:03 +00:00
Sign in to join this conversation.
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: disinto-admin/disinto#282
No description provided.