Skip to content

chore: promote auto-classify Deploy-from-Status sync to main - #45

Merged
LukasWodka merged 2 commits into
mainfrom
develop
May 15, 2026
Merged

chore: promote auto-classify Deploy-from-Status sync to main#45
LukasWodka merged 2 commits into
mainfrom
develop

Conversation

@LukasWodka

Copy link
Copy Markdown
Contributor

Carries fix#44 to main. Keeps the Deployment environment view accurate going forward.

LukasWodkaand others added 2 commits May 15, 2026 11:46
…set"
Status is the source of truth for an item's location in the deploy
pipeline; Deploy environment should always track it. Previously the
cron only filled Deploy when unset and never reconciled drift, which
meant items whose Status got updated by paths other than
advance-deploy-env (closure-router on issue close, manual drag-and-
drop, one-off backfills) ended up with stale Deploy values.
Audit on 2026-05-14 found 311 of 449 Prod items pointing at the wrong
Deploy environment — the "Deployment environment" board view was
showing hundreds of Prod cards in the dev/staging columns.
Mapping (Status -> Deploy env):
Backlog / Ready / In progress / Code review / Cancelled -> none
FR on dev / Ready for staging -> dev
FR on staging / Ready for prod -> staging
Prod -> prod
advance-deploy-env still does the immediate update on push events;
this cron is the safety net for everything else.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…rom-status
fix(auto-classify): sync Deploy env from Status instead of "set if unset"
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@LukasWodka@divyasinghds