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

Only htmlize on master branch #690

Merged
merged 1 commit into from
Jan 5, 2022
Merged

Only htmlize on master branch #690

merged 1 commit into from
Jan 5, 2022

Conversation

ice1000
Copy link
Member

@ice1000 ice1000 commented Jan 5, 2022

Also promote the rendered version in README w/ some adjectives (glorious, clickable) stolen from the stdlib.

Special thanks to @brendanzab

Also promote the rendered version in README w/ some adjectives stolen from the stdlib
@ice1000 ice1000 linked an issue Jan 5, 2022 that may be closed by this pull request
@ice1000 ice1000 mentioned this pull request Jan 5, 2022
@brendanzab
Copy link

Nice, glad it actually seems to work in practice!

@mortberg
Copy link
Collaborator

mortberg commented Jan 5, 2022

Amazing! Thanks a lot for fixing this so quickly!

@mortberg mortberg merged commit 5499226 into master Jan 5, 2022
@ice1000 ice1000 deleted the QAQ branch January 5, 2022 21:21
@ecavallo
Copy link
Collaborator

ecavallo commented May 9, 2022

Is there a reason why only the "Deploy to GitHub Pages" step was restricted to master, and not the "Htmlize cubical" step as well?

@ice1000
Copy link
Member Author

ice1000 commented May 9, 2022

Is there a reason why only the "Deploy to GitHub Pages" step was restricted to master, and not the "Htmlize cubical" step as well?

Reason? Yes. Good? No. One may argue that it makes sense to check if it's possible to generate the html files as nobody said type checking guarantees it, but probably the truth is that I forgot to.

@ecavallo
Copy link
Collaborator

ecavallo commented May 9, 2022

😄 I think it's safe enough to assume the generation will work, so I'll make a new PR to add the check there. Looks like it will only save a minute or two of CI time, but we may as well.

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

Successfully merging this pull request may close these issues.

Problem with CI
4 participants