-
Notifications
You must be signed in to change notification settings - Fork 540
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
Publish GitHub Page with GitHub Action #32
Conversation
TikZ graph was not rendered correctly. @fennecJ, can you give a hint? |
I tryied to use @focaaby 's action script, and my TikZ graph was not rendered correctly, either. As I mentioned in #27 , xu-cheng/texlive-action worked well and rendered the page correctly. |
Umm...
They are not the same thing. Switching from workflows to workflows is just switching the environments that other defined, why don't we just created the environment for us? |
@Hsins |
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.
Read this carefully: https://chris.beams.io/posts/git-commit/
- Wrap the body at 72 characters
Don't use markdown syntax inside git commit message.
For the sake of naming consistency, rename |
The message is too long:
Wrap the body at 72 characters. |
Add a new Github Action to publish to the GitHub page. Use twtug/lkmpg image for reproducibility. Ref: - sysprog21#27 - https://github.com/TeXtw/docker-lkmpg
Thank @focaaby for contributing! |
I was not aware of the HTML generation on GitHub Pages. Here are the configurations: @focaaby, how should I make changes? |
For the sake of naming consistency, both 2 script files should be ended with
It seems .yaml is better choise. |
@jserv |
It works for me now. Thanks! |
Use #20
makefile
html
directory as release HTML assets.References: