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

Invalid datetime format error upon using this template #1

Closed
birdybro opened this issue Jul 16, 2024 · 7 comments
Closed

Invalid datetime format error upon using this template #1

birdybro opened this issue Jul 16, 2024 · 7 comments

Comments

@birdybro
Copy link

See the logs for the default behavior currently.

https://github.com/birdybro/birdybro.github.io/actions/runs/9950026929/job/27487229296

@birdybro birdybro changed the title Invalid datetime format error upon using as template Invalid datetime format error upon using this template Jul 16, 2024
@alexvoss
Copy link
Contributor

Um, the log seems to point to a Jekyll build?

@birdybro
Copy link
Author

I clicked use this template to test it out. The instructions don't specify anything else and the material for mkdocs site links directly to this repo. Has anyone else used this as a template so far so I could compare to see what they did to fix this?

@alexvoss
Copy link
Contributor

You cloned the template into your own repository and a Jekyll build ran? That does seem odd but it looks like by adding a GitHub Actions configuration, you are now actually running a MkDocs build and are running into the next problem, which is progress.

Error: MkDocs encountered an error parsing the configuration file: while constructing a Python object
cannot find module 'ext.slugs' (No module named 'ext')
  in "/home/runner/work/birdybro.github.io/birdybro.github.io/mkdocs.yml", line 22, column 21

This comes from the custom slug function example in the tutorial. If you don't need that then you can simply remove that declaration from the plugin configuration in mkdocs.yml. If you do want to use this, you will need to set PYTHONPATH=. in your environment so that the code in ext/ is found.

I should probably add this to the description of the template as well as to the tutorial.

@birdybro
Copy link
Author

Thanks!

Yeah I was basically testing it blind on purpose since I just wanted to fire up the blog feature and try it out.

Not sure why this jekyll page thing is happening. I got the ci action worked out, had to open up permissions as well as do what you said. Also had to comment out the meta plugin since that's insiders only.

@birdybro
Copy link
Author

Oh I think I know why, because the whole $github_username.github.io is a special repo name so when you enable pages there it might be pushing it as a jekyll build no matter what.

@birdybro
Copy link
Author

https://github.com/birdybro/blogtest - tried a repo rename, that's not it... hrmm

@birdybro
Copy link
Author

There we go, fixed, changed target branch of pages settings to gh-pages, now I'm starting to remember again. Been awhile since I last set this all up. Thanks!

https://birdybro.github.io/blogtest/

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

No branches or pull requests

2 participants