Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to push .nojekyll file to remote gh-pages branch #315

Closed
rxliuli opened this issue Aug 12, 2019 · 3 comments
Closed

Unable to push .nojekyll file to remote gh-pages branch #315

rxliuli opened this issue Aug 12, 2019 · 3 comments

Comments

@rxliuli
Copy link

rxliuli commented Aug 12, 2019

image

The .nojekyll file is included in the doc directory, but cannot be pushed to the gh-pages branch using the command gh-pages -d docs

The directory of the gh-pages branch on the remote GitHub

image

GitHub Repo

@rxliuli
Copy link
Author

rxliuli commented Aug 12, 2019

Ok, just add the parameter -t true. . .

@rxliuli rxliuli closed this as completed Aug 12, 2019
jamesplease added a commit to jamesplease/Next-gh-page-example that referenced this issue Mar 21, 2020
@k-funk
Copy link

k-funk commented May 6, 2020

Would be great to have this -t true option documented. I don't think many people are using this library for publishing jekyll sites, and would think that a including a .nojekyll file at root might even be a default. I wasn't even aware of why my site wasn't serving a directory generated by webpack: :repoName/_/node_modules/...

Kurdiumov added a commit to Kurdiumov/quote-of-the-day that referenced this issue Dec 26, 2020
francisyzy added a commit to HavenOfExcellence/template-guide that referenced this issue Apr 7, 2021
lucasantarella pushed a commit to CompliantInnovation/website-gh that referenced this issue Mar 16, 2023
@mmtolsma
Copy link

mmtolsma commented May 4, 2024

Thank you for this.

My issue was that running npm run build was not adding the .nojekyll file to my build (what you've named docs) folder. I had to do the following in my package.json:

"scripts": {
  "build": "vite build && copy .nojekyll build",
  "deploy": "npx gh-pages -d build -t true",
  ...
},

aminya added a commit to aminya/gh-pages that referenced this issue Aug 26, 2024
Whenever a user specifies a directory, they expect the dotfiles to be served as they exist on the file system. No web standards or conventions specifies otherwise. The previous default was surprising and as you see in the issue tschaub#315, has caused issues for many users.

This PR changes the default to true making this behaviour opt-in.
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

No branches or pull requests

3 participants