Skip to content

ci: add workflow_dispatch triggers to deploy and tag workflows#264

Merged
amis92 merged 1 commit intomainfrom
fix/workflow-dispatch
Feb 28, 2026
Merged

ci: add workflow_dispatch triggers to deploy and tag workflows#264
amis92 merged 1 commit intomainfrom
fix/workflow-dispatch

Conversation

@amis92
Copy link
Copy Markdown
Member

@amis92 amis92 commented Feb 28, 2026

Problem

The chatops /deploy\ command fails with:
\
Command 'deploy' is not configured for the user's permission level 'none'.
\\

The \SLASH_COMMAND_DISPATCH_TOKEN\ PAT used by \peter-evans/slash-command-dispatch@v5\ to check commenter permissions appears to be expired or have insufficient scopes.

Solution

Add \workflow_dispatch\ triggers with typed inputs to both \deploy-command.yml\ and \ ag-command.yml. This allows triggering deployments directly:

\\�ash

Deploy to GitHub Packages

gh workflow run deploy-command.yml -f ref=v0.14.0 -f env=github

Deploy to all (GitHub + NuGet)

gh workflow run deploy-command.yml -f ref=v0.14.0 -f env=all

Deploy and tag

gh workflow run deploy-command.yml -f ref=main -f env=all -f tag=true
\\

Or via the Actions UI with dropdown inputs.

Other fixes

  • Guard chatops-specific steps (PR comment updates) with \github.event_name == 'repository_dispatch'\
  • Fix CI artifact upload path (\�rtifacts/packages/release\ → \�rtifacts/package/release)

- Add workflow_dispatch with inputs to deploy-command.yml and tag-command.yml
  so they can be triggered via gh CLI or Actions UI without chatops PAT
- Guard chatops-specific steps (comment updates) with event_name check
- Fix CI artifact upload path (artifacts/packages → artifacts/package)

The SLASH_COMMAND_DISPATCH_TOKEN PAT appears expired, causing
'permission level none' errors. workflow_dispatch bypasses this.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@amis92 amis92 merged commit 32cc5d5 into main Feb 28, 2026
4 checks passed
@amis92 amis92 deleted the fix/workflow-dispatch branch February 28, 2026 14:49
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