-
Notifications
You must be signed in to change notification settings - Fork 5
Set up deployment #519
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
Set up deployment #519
Conversation
| working-directory: site | ||
| run: hugo --minify | ||
|
|
||
| - name: Deploy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, I don't understand the idea. As we discussed vocally, this site is deployed in a "classic" way. I.e. by pushing the content to master.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, I've added this information to the pull request description.
The “classic” way by pushing the content to master will work for Jekyll implementation, but not for Hugo. Here the script builds the site and placed it in the gh-pages branch.
This PR addresses #485 and #484.
This PR brings such changes:
scripts._code/samplesproject configuration. They will now be used in documentation #53.configuntil it is needed to build samples version 2.buildSrcwith the Gradle build for now.gh-pagesbranch. We need to use it because GitHub Pages automatically builds only sites built in Jekyll, not in Hugo.