This is my go-to tutorial for stringing together GitHub Actions and Google Cloud Platform.

The GitHub Engineering team recently completed a gradual transition away from jQuery and wrote in-depth about the experience. There’s a lot of good detail in the post, but I’m particularly fond of this bit:

As part of our refined approach to building frontend features on GitHub.com, we focused on getting away with regular HTML foundation as much as we could, and only adding JavaScript behaviors as progressive enhancement. As a result, even those web forms and other UI elements that were enhanced using JS would usually also work with JavaScript disabled in the browser. In some cases, we were able to delete certain legacy behaviors altogether instead of having to rewrite them in vanilla JS.

Stick around through the end of the article for more on how the team is using Custom Elements to enhance the user interface.

GitHub added the ability for project maintainers to add issue and pull request templates to projects.

To add an Issue template to a repository create a file called ISSUE_TEMPLATE in the root directory. A file extension is optional, but Markdown files (.md) are supported. Markdown support makes it easy to add things like headings, links, @-mentions, and task lists to your templates.

Thinking this will prove quite useful on some of my projects.

JavaScript and CSS Asset Compression for Production Rails Apps