benbalter

Ben from GitHub here. We don't offer an SLA for GitHub Pages (or GitHub.com generally).

We've talked a bit about our typical traffic in the past (https://github.com/blog/1992-eight-lessons-learned-hacking-o...), but suffice to say, we host some highly trafficked sites like the Bootstrap documentation.

If your blog isn't on that scale, and conforms to our terms of service (https://help.github.com/articles/github-terms-of-service/#g-...), we generally don't enforce hard usage quotas, but if you're concerned, feel free to reach out to support@github.com any time.

It does! https://github.com/benbalter/licensee/blob/master/lib/licens...

It does! https://github.com/benbalter/licensee/blob/master/lib/licens...

> A couple months ago, the entire thing collapsed on my face and we went with gitlab instead. Why? Because github's sales team f*ed it up. Apparently, the $5k minimum order was too small for them to care (at least that's what my side says). Too bad, I really wanted to get them in the door.

Ben Balter from GitHub's government team here. I'm sorry to hear we let you down. Please let us make it up to you. You (or anyone else) should feel free to reach out to me any time at government@github.com, and I'll personally help navigate the process.

For what it's worth, we care a lot about the experiences of all our users, whether you're a developer using the GitHub.com front end, a system administrator spinning up GitHub Enterprise, or a COTR procuring a license for your agency. I'm not part of the Sales team. In fact, my full-time job is to help empower those working to "fix/modernize gov't tech from the inside", and a big part of that over the past year or so has been seriously leveling up the user experience for government and other large enterprises.

To help here, we now have a dedicated government team (https://government.github.com) that makes sure our front-line sales reps and supportocats are conversant in "govspeak", a semi-private government peer group (https://github.com/government/welcome) to collaborate on best practices, and are streamlining the procurement process for government with invoicing and standardized contract vehicles (and now FedRAMP support as part of AWS). I'd love your input on how we can do better.

Yep. The `.nojekyll` option has been around since 2009: https://github.com/blog/572-bypassing-jekyll-on-github-pages

To be specific, all sites are processed through Jekyll, unless you add a `.nojekyll` file. Non-Jekyll files (like HTML or CSS) are passed transparently through Jekyll untouched. Adding the dashes to the file header simply tells Jekyll to work its magic.

Knew we should have used a bubble sort. Thanks for catching that. https://help.github.com/articles/github-glossary#pull-reques...

It installs Jekyll, and its dependencies, which users would have done normally, but explicitly locks the version into the same version used on the GitHub Pages server, ensuring that your local build environment matches the GitHub build environment as closely as possible. This is especially important when new versions of Jekyll are released (often with new features) and the GitHub pages servers are updated. Builds in one environment may otherwise behave differently from builds in another.