Commits hitch a ride in Remotes
Every commit now has a Share menu. Copy the link, or send it straight to a developer through Remotes. Choose a name, check the preview, and you finish in the conversation.
Also leadingThe biggest story by anyone else. Held off 4 challengers since.

Hover any commit and click the new Share icon. The old link button now lives in a menu. Two items wait there. They are Copy link, which still answers to your keyboard shortcut, and Send in Remotes. Pick the second, type a developer's name, and choose them. A dialog asks "Send commit to @handle?" with the commit card as a preview. Cancel sends nothing. Hit Send, and you land in that conversation with the link already posted.
Credit MrPunyapal, who wired the share menu, the developer picker, and the confirmation together. The picker returns up to eight matching developers per search. Send appears only when you are signed in, Remotes is on, and the commit is approved. Pending and rejected commits still offer Copy link. What travels is the commit's full permalink, host intact, sent as an ordinary message. The server also knows this is a share, so it can mark people you cannot reach yet.
There is one catch. The share picker is stricter than the ordinary message picker. If either of you has a request still waiting to be merged, that developer is greyed out with "can't push. Merge their request first" or "your request is waiting to be merged." The regular picker lets you start that conversation anyway. Sharing waits until the request is accepted.
Key files · #1164
- resources/
js/ commit-secondary-actions.tsxcomponents/ - resources/
js/ search-dialog.tsxcomponents/ - resources/
js/ quoted-commit.tsxcomponents/ - app/
Queries/ RemoteCandidatesQuery.php - app/
Http/ ListRemoteCandidatesRequest.phpRequests/ - app/
Http/ RemoteCandidateController.phpControllers/ - tests/
Unit/ CommitShareActions.test.tsx - KNOWLEDGE_BASE.md