Skip to content

Fix release workflow: checkout gh-pages to a separate path - #94

Merged
vpelikh merged 1 commit into
mainfrom
checkout-gh-pages-to-a-separate-path
Aug 28, 2026
Merged

Fix release workflow: checkout gh-pages to a separate path#94
vpelikh merged 1 commit into
mainfrom
checkout-gh-pages-to-a-separate-path

Conversation

@vpelikh

@vpelikh vpelikh commented Aug 28, 2026

Copy link
Copy Markdown
Owner

The release job checked out the gh-pages branch in-place (workspace root) after the composite 'Build and test plugins' action. GitHub runs a composite action's post step at the end of the job, by which point the working tree had been swapped to gh-pages content (which has no .github), so the runner could not find the action.yml and the post step failed with 'Did you forget to run actions/checkout before running your local action?'.

Check out gh-pages into a dedicated 'gh-pages' subdirectory and cd into it for the publish step, keeping the workspace root (and its .github) intact for the whole job including the composite action's post step.

The release job checked out the gh-pages branch in-place (workspace root) after
the composite 'Build and test plugins' action. GitHub runs a composite action's
post step at the end of the job, by which point the working tree had been swapped
to gh-pages content (which has no .github), so the runner could not find the
action.yml and the post step failed with 'Did you forget to run actions/checkout
before running your local action?'.

Check out gh-pages into a dedicated 'gh-pages' subdirectory and cd into it for the
publish step, keeping the workspace root (and its .github) intact for the whole
job including the composite action's post step.
@vpelikh
vpelikh merged commit a6e11e9 into main Aug 28, 2026
5 checks passed
@vpelikh
vpelikh deleted the checkout-gh-pages-to-a-separate-path branch August 28, 2026 09:59
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