-
-
Notifications
You must be signed in to change notification settings - Fork 41
Bradley is back from time off so let’s move him back to current team. #74
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
Conversation
That should fix the padding. |
Bradley is back from time off so let’s move him back to current team.
I merged, but I cannot deploy the changes. |
Thanks! I can't deploy, either...I get:
@JonRowe, can you take a look? |
Odd, it built for me, although I got several bourbon sass warnings Bradley Schaefer
|
Deployed |
It builds fine for me so it might be a gem version issue? |
My gems for comparison https://gist.github.com/JonRowe/4a9bffd7e0bcbfa920ab |
Somehow the deploy got borked, @JonRowe. Notice the lack of styles at http://rspec.info/documentation/3.3/rspec-core/. Want to try re-deploying? I tried but I'm still getting the error message. |
Working on it |
I'm not sure when this was last working, previous commits on master seem to have the same issue, the fix I worked up before doesn't seem to be the one we used in the end (as the plugin hasn't been used to generate the doc files so the css is in the wrong place) I have a solution involving using middleman's proxy directive but at the moment it causes my middleman build to fail for the "latest" files |
Previously we had seen it fail on some deploys but then work on a redeploy. Is that no longer the case? |
Doesn't seem to be |
Any idea how we fixed this in the end? I can't find evidence of anything but the plugin I wrote, but that doesn't seem to have been used... |
Nope, sorry. |
I can't get this to render right, though:
Anyone with more CSS know-how than I have want to take a stab at fixing it?
/cc @rspec/rspec