You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [⭐️ Static Site Generators with Node.js](#%EF%B8%8F-static-site-generators-with-nodejs)
116
117
- [⭐️ Gatsby](#%EF%B8%8F-gatsby)
@@ -649,6 +650,49 @@ jobs:
649
650
...
650
651
```
651
652
653
+
### ⭐️ Release Strategy
654
+
655
+
cf. [support: execution from hashref disabled/broken vs GitHub Actions Security Best Practice? · Issue #712 · peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages/issues/712)
656
+
657
+
Our project builds and provides build assets only when creating a release. This is to prevent the user from executing this action with a specific branch (like main). For example, if we maintain build assets in the main branch and users use this action as follows, a major release including breaking changes will break the CI workflow of the users silently.
658
+
659
+
```yaml
660
+
- uses: peaceiris/actions-gh-pages@main # Bad example!
661
+
with:
662
+
github_token: ${{ secrets.GITHUB_TOKEN }}
663
+
publish_dir: ./public
664
+
```
665
+
666
+
In this project, a major tag (e.g. v3) is guaranteed to contain no breaking changes. But, we recommend using a tag or a commit hash for the stability of your workflows.
0 commit comments