search

mkdocs / mkdocs-bootswatch-classic

"Classic" versions of the Bootswatch-based MkDocs themes
BSD 2-Clause "Simplified" License
0 stars 3 forks source link

Update Travis CI config #1

Closed jimporter closed 2 years ago

jimporter commented 4 years ago

When preparing this repo, I didn't touch the .travis.yml config. Who's the right person to make these changes?

d0ugal commented 4 years ago

That might be me. What changes are needed?

jimporter commented 4 years ago

@d0ugal I think all that's needed is to enable this repo in the Travis CI interface and update the doc deployment bits here:

https://github.com/mkdocs/mkdocs-bootswatch-classic/blob/177fefa6ccadf76e825a3d0255a9cd36d4a9c23c/.travis.yml#L40

waylan commented 4 years ago

@d0ugal the deployment of mkdocs-bootswatch failed at the same stage (GitHub Pages deployment) this past weekend. I didn't investigate why and just manually deployed the docs. But I wonder if perhaps the old GitHub token is no longer valid.

I also manually deployed the docs for mkdocs-bootswatch-classic. The only thing left to do is an actual release. Which PyPI account have the other projects been uploaded with? Whoever has control of that account will need to set up mkdocs-bootswatch-classic as well.

d0ugal commented 4 years ago

👍🏼 I’ll try and get to this as soon as I can. My second kid was born two days ago, so the timing couldn’t be much worse!

jimporter commented 3 years ago

@waylan @d0ugal Just wanted to get this back on your radar. No worries if you're too busy with other things though; this has definitely been a rough year!

waylan commented 3 years ago

@jimporter thanks for the reminder. We just switched mkdocs/mkdocs over to use GitHb actions. We should probably do the same here. And as I have full admin access now, I can do that myself. Just need to find some time to work on it. 😉

jimporter commented 3 years ago

Cool! That plus a release on PyPI and this project should be pretty much "done". I don't expect that there will be a lot of maintenance work required for it since the theme data is all self-contained in this repo now, so theme changes in mkdocs/mkdocs won't affect anything here.