Context
The organization-level reusable Trunk workflow was refreshed in #404:
- deprecated Trunk web-app upload wiring was removed from active use
- the reusable workflow now uses current Trunk Code Quality behavior
- callers should use one check job instead of separate
check/upload jobs
- callers should declare explicit permissions and concurrency
z-shell/zunit adopted the new caller shape in z-shell/zunit#7 and passed CI after the org workflow was merged.
Scope
Audit and update Z-Shell repositories that still call:
uses: z-shell/.github/.github/workflows/trunk.yml@main
Prioritize repositories with existing Trunk workflows and recent maintenance activity.
Initial rollout candidates
z-shell/zsh-lint
z-shell/zsh
z-shell/z-a-meta-plugins
z-shell/zsh-fancy-completions
- other repos found by code search using the org reusable workflow
Desired caller shape
- one
Trunk Code Quality job
- no deprecated
upload job
- no
TRUNK_TOKEN / trunk-token upload path unless a future supported Trunk feature requires it
- explicit top-level
permissions: contents: read
- explicit job permissions where annotations/checks need them
concurrency for push/PR workflows
arguments: --no-progress where useful for readable logs
Suggested tracker fields
- Item type: Task
- Priority: Medium
- Effort: Medium
- Status: Backlog
Context
The organization-level reusable Trunk workflow was refreshed in #404:
check/uploadjobsz-shell/zunitadopted the new caller shape in z-shell/zunit#7 and passed CI after the org workflow was merged.Scope
Audit and update Z-Shell repositories that still call:
Prioritize repositories with existing Trunk workflows and recent maintenance activity.
Initial rollout candidates
z-shell/zsh-lintz-shell/zshz-shell/z-a-meta-pluginsz-shell/zsh-fancy-completionsDesired caller shape
Trunk Code QualityjobuploadjobTRUNK_TOKEN/trunk-tokenupload path unless a future supported Trunk feature requires itpermissions: contents: readconcurrencyfor push/PR workflowsarguments: --no-progresswhere useful for readable logsSuggested tracker fields