It is hard to have conversational threads because the reply button picks the author alone. Should it also add the mentioned devs from the last commit to the next reply?
- Yes64%, 7 votes
- No - as is now36%, 4 votes
11 votesFinal results
Commit
aa77108
I'm confused, what are you referring to? The reply button should pick in this order:
1. Direct reply
2. Author
3. Commit thread participants
4. Everyone else
See https://github.com/dev-null-sh/dev-null.sh/pull/750…
GitHubfeat: prioritize mention suggestions by conversation by xHeaven · Pull Request #750 · dev-null-sh/dev-null.shReplies and quotes currently suggest the same people as an unrelated new commit. Prioritize the people in the conversation while preserving the existing name/username matching and safety filters. ...
On X, when you hit reply, you automatically reply to all thread participants. You don't have to select their handles from the dropdown manually
So Mark doesn't get a notification of this message, right? I think that's confusing indeed.
One thing I do like on X, is that you can deselect people from the 'Replying to'. It's just not very obvious there, and most people don't know/don't use it.
Maybe it's as simple as…
Yes, @xHeaven didn't get the notification. I think X's way is simpler and intuitive.
Hmm, okay, I might look into this. Unless you send a PR first đź‘€ It should stay deselectable, though.
commit aa77108
Done. You will appreciate. https://github.com/dev-null-sh/dev-null.sh/pull/1238
GitHubfeat: add participant selection to commit replies by richardkeep · Pull Request #1238 · dev-null-sh/dev-null.shShow “Replying to” above the composer for replies with multiple recipients. Clicking it opens a picker to uncheck participants while keeping the commit author selected. The logged-in user is exclud...