Mention a GitHub organization in a commit and the handle now opens a page for it, mirrored from GitHub. If a developer owns that handle, the developer still wins.
Top storyTook the lead from Join sheet offers a Safari escape hatch#1218. Mentioning an organization in a commit now opens a page showing its GitHub profile, and a new command links organizations in older commits. Held off 2 challengers since.
mnapoli, who filed the change, pictured in the contributor’s own avatar.
You type a commit that thanks @laravel and send it. Once the commit is approved, the handle turns blue in the body, and clicking it lands you on a page with the organization's square avatar, name, description, location, website, and a link back to GitHub. No account to set up, no profile to fill in.
Credit goes to mnapoli, who taught commits to ask GitHub about the handles they mention. Approval queues the lookup, which makes at most five GitHub requests per commit and skips handles that already belong to a developer. A handle GitHub calls an organization gets a page, refreshed at most once a day. A handle that isn't one isn't asked about again for a day. Autocomplete offers up to three known organizations after the people, once you've typed a letter. To catch up old commits, run php artisan commits:link-organizations, which walks approved commits and stops when GitHub's rate limit runs low.
There is one catch, though. The page is only a header for now. It shows the GitHub profile and an empty log that promises following and community commits later, so there is nothing to follow and no commits listed under the organization yet.
FixesGuests opening the device approval page now get sent straight to GitHub sign-in and come back to that page, instead of landing on the log to hunt for Sign in. #1128
FixesCode blocks now end only on a fence at least as long as the opening one, so a four-backtick block can hold a three-backtick sample instead of spilling out. #1227
FixesRelated commits now chain in their own graph canvas and end on a dot below the last card, instead of a rail trailing off the edge. #1257
FixesGitHub sign-in now sends you back to the login page for one retry when the flow finishes in a different browser, instead of showing the sign-in error immediately. #1259
FixesIn-app browsers now show the GitHub sign-in button plus a hint to open the page from the app's menu, pointing at X's ⋮ on iOS, instead of a link apps ignore. #1260
Tap a link from X or Instagram and the guest join sheet now offers to reopen the page in Safari or your Android browser, where GitHub may already be signed in. No password, no 2FA code.
You tap a post in X, land on /dev/null, and the join sheet slides up with a new line. It says, "You're in X's browser, which isn't signed in to GitHub." Under it sit two choices, Open in Safari and Join with GitHub here instead. Tap the first and the same page reopens in Safari, where your GitHub session, saved password and passkey already live.
Credit goes to mnapoli, who taught the sheet to read the browser it wakes up in. It knows seven apps by name, including X, and catches unnamed web views by the Safari token they drop on iOS or the wv marker Android adds. iOS gets a link that asks for Safari. Android asks the system for the default browser. Tap it and, if the page is still on screen 1.5 seconds later, the text switches to tell you to use the app's ⋯ menu. Desktop and ordinary phone browsers keep the old single button.
One catch. It only spots apps that give themselves away. Apps that draw the page inside Safari's own view look exactly like Safari, so the sheet hands you the plain Join with GitHub button and no offer at all. You're back to hunting for the app's menu yourself.
Fenced code can now label itself with a file path, and the block header shows that path instead of the language. Add a title after the language and your snippets stop being anonymous.
You paste a snippet into a commit, open the fence with three backticks and php, and tack on title="app/Models/User.php". The little header above the code now reads app/Models/User.php instead of php. Highlighting is untouched, the copy and wrap buttons sit where they always did, and a long path cuts off with an ellipsis while the full one waits in the tooltip.
Credit goes to raz-iacob, who taught the fence reader at both ends, the PHP that highlights on the server and the TypeScript that previews while you type, to split off the language and read the rest as key="value" pairs. title wins, filename is the alias, the first of a repeated key wins, and an empty title falls through to filename. Ranges like {1,3} and tab="Pest 4" get read and dropped, so old blocks look exactly as they did. The label is 11-pixel monospace in the same 32-pixel header.
One catch. Only double quotes count. Type title='app/Models/User.php' with single quotes and the header just keeps showing php, without a word of complaint.
You are walking a busy log with j and k, and a commit catches your eye. Hit s and the star fills in, the count ticks up one, and the star gives a little pop. Hit s again and it goes away. Hover the star and the tooltip shows the s key right beside the word Star, so you never have to guess. The same trick works inside a reply. It stars the reply, not the card around it.
Credit 0z3, who plugged the star control into the keyboard map that already handles reply, quote, and copy-link. The map clicks the first star control inside whatever commit or reply holds focus, which is why replies behave. For the jumps, press g and then n, m, or * within one second. That takes you to Notifications, Remotes, and Starred. That makes seven destinations behind g, counting your log, trending, profile, and settings. The m key answers only while Remotes is switched on, and guests who try g n or g * land on sign-in.
One catch. Your own commits show a star count, not a star toggle, so parking on one and pressing s does nothing at all. The count just sits there, and clicking it opens the list of who starred you. Star other people's commits. Yours you can only watch.
Guests now see how many developers are on /dev/null before they sign in. The count is rounded down and refreshed hourly. It appears in the desktop sidebar card and the phone join sheet.
Sign out, open Trending on a laptop, and look at the sidebar. The "New to /dev/null?" card now reads "12,000+ developers are already here. Sign in with GitHub to follow them, star commits, and join the conversation." On a phone, the sheet that slides up from the bottom has a new title, "Join 12,000+ developers." The button still says "Join with GitHub."
Credit goes to mnapoli, who taught the sign-in pitch to count the room. The app counts every account, skips banned ones and the two bot accounts, then rounds down. It rounds to the nearest hundred below a thousand and to the nearest thousand from a thousand up, so 12,000+ stays honest until 13,000. It caches the total for 3,600 seconds, so one count serves every guest for an hour, and signed-in readers never see it. Below a hundred, the rounded number is zero and the old wording quietly returns.
One catch. The number lives in the wide desktop sidebar and the phone sheet, and nowhere in between. Drag your window to tablet width, roughly 768 to 1,279 pixels, and both disappear, so you can browse as a guest and never learn how many developers are here.
