Skip to content

pm: fix audit CI failures (real drift + missing label)#128

Merged
hanwencheng merged 1 commit into
mainfrom
pm/automation-foundation
May 24, 2026
Merged

pm: fix audit CI failures (real drift + missing label)#128
hanwencheng merged 1 commit into
mainfrom
pm/automation-foundation

Conversation

@hanwencheng
Copy link
Copy Markdown
Member

Summary

Fixes two CI failures from the first pm-workflow-audit.yml run on main (after #127 merged):

  1. Real drift detected: Auto-archive items workflow is enabled on the project, but expected-workflows.json marked it should_be_enabled=false. The operator turned it on via the UI (the recommended state per the original note). Flip the expected state to true so audit reports 11/11 match.
  2. Issue-creation step crashed: could not add label: 'kind/automation' not found. The repo has 7 kind/* labels in pm/labels.json but no kind/automation. Switch the drift-issue creation step to kind/devx (which exists and fits — automation tooling = dev experience).

File diff

.github/workflows/pm-workflow-audit.yml | 2 +-
pm/expected-workflows.json              | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)

Note on commit count

The "Commits" tab will show 7 commits but only 1 is new (eaffdf5). The other 6 are the same commits that #127 squash-merged onto main. GitHub's file-level diff is the source of truth — only 2 files changed.

Test plan

  • After merge, the daily cron at 14:00 UTC should report ok check-workflows: 11 matched, 0 mismatches and skip the issue-create step entirely
  • Optional: gh workflow run pm-workflow-audit.yml --repo litentry/agentKeys to verify immediately
  • If drift is ever detected in the future, the issue-create step will now succeed with kind/devx,priority/p2 labels

Two issues surfaced from the first pm-workflow-audit.yml run on main:

1. The audit reported real drift: Auto-archive items workflow is enabled
   on litentry/projects/19, but expected-workflows.json marked it as
   should_be_enabled=false. The operator enabled it via the UI (which
   is the recommended state per the original note). Flip the expected
   state to match reality.

2. The drift-issue-creation step failed: "could not add label:
   'kind/automation' not found". The repo doesn't have a kind/automation
   label — only the 7 in pm/labels.json. Switch to kind/devx since the
   automation health belongs to dev experience.

After this, the audit should report 11/11 match and the issue-create
step won't fire (but is defensively label-correct for future drifts).
Sign up for free to 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.

1 participant