-
Notifications
You must be signed in to change notification settings - Fork 0
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
Styling for error pages #1
base: master
Are you sure you want to change the base?
Conversation
My Rails is a little rusty, so I'll need a little help here. I've tried adding this to
I couldn't see any difference. I still need to run |
If you precompile the assets in the initializer, that means that starting the server should be enough to make those assets show up. Unfortunately, just that line won't do it -- adding those to the list of assets to compile only helps if you're actually compiling assets, which doesn't happen by default when you start the server. I'm not sure how you run a Rake task on app startup outside of Rake, nor how you would run the asset precompile without running the Rake task. But presumably you'd need to do one of those two. |
Grouping benchmarks
Manually run only latest commit
…sentry Replace bugsnag with Sentry
Add ssh method to support PG suite
Remove double assignment to initiator
Add temporary rake task
1ebe381
to
8de94db
Compare
I'm trying to fix ruby-bench#46
The pull request is currently just a first draft. I intend to build something
together with you people.
Please take a look at my modified 404 page.
I've started from the HTML for the "Contributing" page and changed it to make a 404 message. Is this a step in the right direction? I mean... In the visual style sense?
This pull request was sent anonymously through anonydog.
There is a person behind the curtain. But the bot hides the real author.
Anonydog wants to allow people to watch how Github project maintainers behave when they don't know who is behind the keyboard.
But the code is still in its early testing stages. I want to ask you to please spend some minutes trying to identify who is the real author of this pull request. In case you manage to do it, please open an issue with the
deanonymization
label in theanonydog/anonydog
project telling me how did you do it.