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
Repositories that use GitHub Pages can now build and deploy from any branch. Publishing to the special gh-pages branch will still work the same as it always has, but you can now choose a different branch in your repository as the publishing source. This functionality also removes the hardcoded dependency on user and organization pages having a master branch.
v3 automatically add .nojekyll file to only master and gh-pages branch now. From v4, this action will add .nojekyll file automatically to any branch. Since this is a breaking change, this change will be released as v4.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
This issue has been LOCKED because of it being resolved!
The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.
Is your feature request related to a problem? Please describe
From #437
cf. #436
v3 automatically add
.nojekyll
file to only master and gh-pages branch now. From v4, this action will add.nojekyll
file automatically to any branch. Since this is a breaking change, this change will be released as v4.Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: