GitHub @github

The AI-powered developer platform to build, scale, and deliver secure software. github.com San Francisco, CA Joined February 2008

Tweets

11K
Followers

2.7M
Following

334
Likes

9K

GitHub @github

8 hours ago

What are your conference essentials? Grab a #GitHubUniverse pass to join us in-person October 28-29 or sign up to join us virtually ⬇️ githubuniverse.com/?utm_source=Tw…

9 7 71 21K 9

View Details

GitHub @github

12 hours ago

GitHub.com has fully moved off CSS-in-JS to CSS Modules, resulting in 55% less server-side render time and 25% faster component init. x.com/i/article/2110…

34 23 355 43K 133

View Details

GitHub @github

a day ago

New in GitHub Transparency data: Learn about government takedown requests and reporting, and get a recap of 2026 state legislative sessions affecting open source. github.blog/news-insights/…

15 13 216 43K 19

View Details

trying something new... i've shared 8 community-requested features we're exploring and would love your feedback. upvote the comments for ideas you'd find useful or reply with your thoughts. github.com/orgs/community…

6 6 30 10K 2

View Details

Dan Wahlin @DanWahlin

2 days ago

Even when the end-to-end tests pass, I sometimes want to see a feature working before I approve a PR. The GitHub Copilot app lets me watch my agent run tests, build the app, and check a filter change in the built-in browser canvas. I can verify the behavior without leaving the app or switching windows. Here's a quick walk-through. 👇

4 5 28 10K 13

View Details

GitHub @github

2 days ago

Psst, pass it around: We have a new and improved badge for GitHub Universe 2026 ✨ Grab your in-person pass and secure a badge. Can't make it? Sign up to join us virtually. ⬇️ githubuniverse.com/?utm_source=Tw…

13 7 101 31K 8

View Details

GitHub @github

2 days ago

⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️ x.com/i/article/2110…

33 14 134 37K 19

View Details

GitHub @github

2 days ago

Cake is always open source #NationalDessertDay

12 6 103 22K 2

View Details

Camilla Moraes @moraes_c_

a week ago

As low-quality contributions increase across open source repositories, more contributors should have the tools to help manage repos. Users with triage, write, maintain, or admin access can now archive PRs.

GitHub Changelog @GHchangelog

a week ago

Users with triage role or higher can now archive and unarchive pull requests. • Archiving closes PRs, makes them read-only, and hides them from public view • Unarchiving restores commenting but does not reopen the PR github.blog/changelog/2026…

1 1 19 14K 3

5 6 29 12K 4

View Details

Sameen Karim @sameenkarim

a week ago

Approvals are now retained for Stacked PRs after stack rebases ✅ Whether you use the "Rebase stack" button or partially merge a stack, as long as the diff doesn't change, PR approvals will be kept even if you have "dismiss stale approvals" turned on

16 31 411 44K 96

View Details

Camilla Moraes @moraes_c_

a week ago

After introducing PR limits, we heard from maintainers dealing with a flood of draft PRs. You can now turn on “Count draft pull requests toward the limit” to include drafts in your repository’s limit. What other controls would help you manage contributions?

5 5 44 18K 7

View Details

GitHub @github

5 days ago

Open the worst pull request you’ve got and try it out 👇 github.blog/engineering/us…

2 0 8 9K 7

View Details

GitHub @github

5 days ago

Any “is the user interacting?” check has to distinguish real user input from scrolls caused by your own side effects.

1 0 4 9K 1

View Details

GitHub @github

5 days ago

One bug that held us back was “don’t correct while you’re scrolling.” It was a timestamp guard, and our own programmatic scrolls refreshed it. Toggle the sidebar, and the diff pane changes width. Wrapped lines reflow, and the surface emits a small scroll as it settles. The guard read that as your input and skipped the correction meant to keep your place. The file you were reading drifted off screen.

1 0 1 2K 1

View Details

GitHub @github

5 days ago

What we shipped is a recurring measurement pass, gated on idle and scoped to roughly 2400px around the viewport. Mounted blocks are ground truth. Observers normally only flag a block for the pass. They don’t write heights themselves. There’s one exception: a visible block resizing because of the user’s action can apply one synchronous correction before paint. That keeps the comment and code below it moving together without reopening the feedback loop.

1 0 2 2K 1

View Details

GitHub @github

5 days ago

For the first design, we gave every dynamic block a ResizeObserver that wrote measured heights back into the layout. We built it, then rejected it. An observer that writes a height back into the layout it’s watching can retrigger itself, and the cost grows with every mounted block.

1 0 11 4K 1

View Details

GitHub @github

5 days ago

A code row is a line at a known height. You can compute the whole geometry up front and never have to correct it. Comments don’t have a predictable height. So we stopped forcing one geometry to serve both, and split the document into two independent height domains.

4 0 19 7K 2

View Details

GitHub @github

5 days ago

Rendering a million-line diff is the easy part. 👀 Comments are what break it. Their height depends on markdown wrapping, expanded details, open reply boxes, and images still loading (none of which you know until you render). Here's how we rebuilt the PR view in the GitHub Copilot app 🧵

58 17 377 96K 81

View Details

GitHub @github

5 days ago

Continuous fuzzing finds real bugs, but it still needs someone to write harnesses, watch coverage, and triage every crash. The GitHub Security Lab built the Fuzzing Taskflow to give that loop to an agent. You point it at a C or C++ repository, and it identifies entrypoints, analyzes the build, crafts harnesses, runs the AFL++ fuzzer, reads coverage, and creates a vulnerability report for each unique bug. Check out how the pipeline works end to end 🔍 github.blog/security/appli…

62 26 270 65K 68

View Details

GitHub @github

7 days ago

In a new survey of 1,039 GitHub users conducted by GitHub and the Yale Program on Climate Change Communication, we found: • 80% were interested in tools for writing more energy-efficient code • 78% wanted to learn best practices for reducing software’s environmental footprint • 74% wanted ways to measure the environmental impact of their software or development process Developers want more efficient software. What many lack is a clear way to find waste, measure improvements, and make the case for fixing it. There’s an opportunity to turn that interest into normal engineering work. 💡 github.blog/news-insights/…