-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Have Travis CI push doc pages? #155
Comments
I think it's perfectly reasonable to purge the gh-pages history occasionally if it gets too bulky, and it's not too hard to set up Travis to publish the site automatically. The only concern I'd have about this is that when you have Travis doing something that relies on the central repo's |
It sounds like @inthenow is going to look into this. @travisbrown do you feel strongly that we shouldn't set it up from Travis? |
No, going ahead sounds good to me!—at a glance it looks like it shouldn't be too hard to set this up with |
http4s publishes from Travis. We call this bash script from after_success. I don't think that's a drop-in solution for cats, but it's a starting point. |
@rossabaker thanks for the head start link and @travisbrown for the tip :) |
The trickiest thing I encountered implementing this is to not prune docs from prior releases. Help may be on the way with sbt/sbt-ghpages#10, but until then, I had to resort to copying code out of the plugin. The API version |
Thanks to the excellent work of @stew and @tpolecat, we now have fancy documentation at http://non.github.io/cats/. It may be tough for us to remember to keep it up to date. Would it be possible/desired to have the Travis CI job for the master branch automatically publish those pages?
I'm not sure if this is tough from a permissions perspective. Also I don't know if there might be an issue with a really noisy git history for the pages that gets bulky when you pull the project?
The text was updated successfully, but these errors were encountered: