-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
build files in git and Github Pages #5
Comments
while you do need to have the html files on GitHub somehow (either on the master branch or on the gh-pages branch), you definitely DO NOT NEED the that said, using GitHub Actions to not have the P.S. you don't need the |
this solution resolves the issue. keeping it open until it is also added to the official documentation. |
Agggr, you're right about About the - |
thats a good point, so lets keep it as is. since that affects people collaborating on some documentation together as well, I think for convenience I'll add an |
it turns out there was a race condition for creating the |
added this section to official docs as well for how to achieve this. again, @LukasForst thanks for the neat solution! |
Thanks! One last thing, you misspelled my name 😄, no biggie though
should be
|
Hi,
I like your work, awesome job! I wanted to setup a simple blog with my code and I noticed that
node_modules
have to be commited in the repo, which is something that I don't like (at least because of the size of the repo).As I'm using Github Pages to host the blog I created Github Action pipeline, that takes the repo without
node_modules
, builds it and deploys it to the separate branchgh-pages
. The benefit is that you don't havenode_modules
andhtml
files, that are automatically generated, in your source code, but rather in the separate branch.I think it is an elegant solution, so I just wanted someone know, that it is possible not to commit
node_modules
to the repo and utilize github actions instead.The text was updated successfully, but these errors were encountered: