actions-marketplace-validations/Gatsby Publish without Jekyll
Build and deploy your Gatsby site to GitHub Pages without Jekyll.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jun 7, 2022
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/meese-enterprises_gatsby-publish-without-jekyll@1ea92992a9a3d70bd222b6e5ef31b6e8afd91bb4 # no releases — HEAD as of 2026-07-12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| access-token | A personal access token needed to push your site after it has been built. | no | — |
| deploy-branch | The branch expected by GitHub to have the static files needed for your site. | no | master |
| deploy-repo | The repo expected by GitHub to have the static files needed for your site. | no | "" |
| gatsby-args | Additional arguments that get passed to `gatsby build`. | no | "" |
| skip-publish | Builds your Gatsby site but skips publishing by setting it to `true`. Helpful for testing/debugging Workflows. | no | false |
| working-dir | The directory where your Gatsby source files are at. `gatsby build` will run from this directory. | no | . |
| commit-message | The commit message used for pushing changes to the deploy branch. | no | "" |
| git-config-name | The name under which the deploy commit is pushed to the deploy branch. | no | "" |
| git-config-email | The email adress under which the deploy commit is pushed to the deploy branch. | no | "" |
Outputs
no outputs