Jekyll has a core team!
Please welcome @qrush (Nick Quaranto) to the core Jekyll team (now consisting of the two of us)! img http://www.gravatar.com/avatar/eb8975af8e49e19e3dd6b6b84a542e26?s=200 He’ll be helping me keep Jekyll active and awesome by assisting…
Please welcome @qrush (Nick Quaranto) to the core Jekyll team (now consisting of the two of us)!
img http://www.gravatar.com/avatar/eb8975af8e49e19e3dd6b6b84a542e26?s=200
He’ll be helping me keep Jekyll active and awesome by assisting with the review and merging of the millions of branches that the amazing open source world has showered upon us.
Also, if you’re serious about having your contributions merged in, please make sure they apply cleanly to the current master branch and open an issue instead of sending a pull request. This will help us keep organized!
The good doctor lives on!
Written by
Related posts
What’s coming to our GitHub Actions 2026 security roadmap
A look at GitHub Actions’ 2026 roadmap, outlining how secure defaults, policy controls, and CI/CD observability harden the software supply chain end to end.
Updates to GitHub Copilot interaction data usage policy
From April 24 onward, interaction data—specifically inputs, outputs, code snippets, and associated context—from Copilot Free, Pro, and Pro+ users will be used to train and improve our AI models unless they opt out.
GitHub availability report: February 2026
In February, we experienced six incidents that resulted in degraded performance across GitHub services.