Skip to content

fix: remove [skip ci] from publish workflow#822

Merged
aaronpowell merged 1 commit intostagedfrom
fix/remove-skip-ci-from-publish
Feb 26, 2026
Merged

fix: remove [skip ci] from publish workflow#822
aaronpowell merged 1 commit intostagedfrom
fix/remove-skip-ci-from-publish

Conversation

@aaronpowell
Copy link
Contributor

The [skip ci] tag in the publish workflow's commit message was preventing downstream workflows (like deploy-website.yml) from triggering on the push to main.

This removes [skip ci] so the website deploy and any other main-branch workflows fire as expected. Verified no other workflows will be unintentionally triggered.

The [skip ci] tag in the publish commit message was preventing
downstream workflows (e.g. deploy-website.yml) from triggering
on the push to main.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings February 26, 2026 05:59
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the [skip ci] tag from the publish workflow's commit message to enable downstream workflow triggering. The publish workflow runs when code is pushed to the staged branch, materializes plugin files, generates marketplace artifacts, and force-pushes the result to main. Previously, the [skip ci] tag prevented any workflows from triggering on that push to main, blocking the website deployment and webhook notifications.

Changes:

  • Removed [skip ci] from the commit message in the publish workflow to allow downstream workflows to trigger on push to main

@aaronpowell aaronpowell merged commit adfdd78 into staged Feb 26, 2026
4 checks passed
@aaronpowell aaronpowell deleted the fix/remove-skip-ci-from-publish branch February 26, 2026 23:12
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.

2 participants