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

Use github action to generate weekly #184

Open
1 of 4 tasks
at15 opened this issue Jan 13, 2020 · 5 comments · Fixed by #185
Open
1 of 4 tasks

Use github action to generate weekly #184

at15 opened this issue Jan 13, 2020 · 5 comments · Fixed by #185
Assignees

Comments

@at15
Copy link
Member

at15 commented Jan 13, 2020

A follow up on #175, we need to generate both md files and html if we want to use github pages.
We have dy-bot to run weekly generator and relies on netlify for running jekll, both can be implemented using github action.

  • Dockerfile that contains latest weekly generator and jekyll
  • create and close issue weekly
  • On issue close, trigger generator, push to master branch
  • Update docs folder for jekyll ... or do we really need it? btw: the theme looks really bad .... Better gh-pages style #1
@at15 at15 self-assigned this Jan 13, 2020
@at15
Copy link
Member Author

at15 commented Jan 13, 2020

btw: @gaocegege why we need to check in the generated html from jekyll? I think both gh-pages and netlify allows you to build from md directly?

@at15
Copy link
Member Author

at15 commented Feb 10, 2020

这个周末我就去做,不咕了,真的。

@at15
Copy link
Member Author

at15 commented Feb 16, 2020

我吃个炸鸡就去写 .w. ....

@at15
Copy link
Member Author

at15 commented Mar 9, 2020

The issue logic is working, but I haven't write the commit and push logic ...

@at15 at15 reopened this Mar 9, 2020
@at15 at15 mentioned this issue Mar 16, 2020
@at15
Copy link
Member Author

at15 commented Mar 18, 2020

Test comment from github mobile @gaocegege

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant