Redirect from non-slash to slash page, fixes #452.

[babruix]

No description provided.

[KyleAMathews]

@babruix this looks great! Thanks!

If you could fix the lint errors real quick, I'll merge and make a new release.

[babruix]

I have fixed eslint issues, but don't have access to netlify build log.

[KyleAMathews]

Awesome, thanks! This will save a lot of people frustration.

Yeah, I enabled the Netlify stuff to start working on the website but haven't quite got to it yet so it's failing because there's nothing for it to do. So we can ignore that error for now.

[KyleAMathews]

Published 0.12.13 🎉

[jlengstorf]

Hiya @babruix! 👋

This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here.

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (We’ve got t-shirts and hats, plus some socks that are really razzing our berries right now.)
2. If you’re not already part of it, we just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. You’ll receive an email shortly asking you to confirm. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again! 💪💜