One of the most requested GitHub features in years and the website looks like it was designed by someone 9 years into a 2 year community college program. https://t.co/Mm1IeyRdy9
@iserflott@matthewisabel Squash merges are my favorite! Each PR in the stack is squashed to 1 commit. We git rebase --onto for each subsequent branch to replay commits from the head branch on top of the squashed commit
Our goal is to make stacks work seamlessly across all of GitHub
That means getting it right so branch protection rules, Actions/CI, code scanning, reviews, rebasing, merging, etc. "just work" as you'd expect
More to come soon 🙏
One of my personal favorite parts has been using the stacks CLI with agents ⚡️
The included skill file shows agents how to use stacks to break up a large diff or build a feature incrementally
Smaller PRs = higher quality code reviews
Merge status in the PR header is beginning rollout, let us know what you think! Lots of improvements to the experience like this coming -- I'm excited!
A little caching goes a long way at GitHub scale
Since the start of the year, code view page loads under 100ms are up around 10x and climbing
This is both a result of caching and a number of other frontend improvements that rolled out to 100% today
The @github UI team has been on 🔥 lately, and they just open sourced one of their key tools: a storybook addon to help you break down performance on a component-level
Internally we use this for detecting janky or slow interactions with components
It supports analysis of six areas
- Frame timing
- Input responsiveness
- Main thread health
- React performance
- Layout stability
- Memory and resources