3 ms·
I agree that it should be easier to find related resources, like the git repo a patch applies to. This is one of the issues prioritized during the alpha, and I'
by ddevault 6y ago
I agree that it should be easier to find related resources, like the git repo a patch applies to. This is one of the issues prioritized during the alpha, and I'll ask for your patience and understanding that it doesn't represent an unfixable flaw - stuff like this is why we still have the alpha designation.
You can already filter by project, though. Here are all the git.sr.ht patches:
https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches?search=prefix%3Agit.sr.ht https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches?search=prefi...
The feature is hinted at in the placeholder text on the search box.
>support dealing with direct feedback and changes that respond to them in a single PR.
Linking multiple versions of a patch together into one cohesive patchset is another thing which is possible in theory and prioritized for the alpha.
>I do, when working on feature branchs. But that's another nonintuitive thing to get people to unlearn and relearn. Which of course, also includes git send-email.
Both of which we have detailed tutorials for!
https://git-send-email.io https://git-send-email.io
https://git-rebase.io https://git-rebase.io
- mixedCase 6y agoWell, for what little it's worth, you've convinced me to give sourcehut a try for a personal project where any of these shortcomings should not pose a problem. You leave me thinking you actually give a shit about not leaving the average person behind and that ease of use is a priority. So if you can eventually couple the simplicity and performance you already have with slight changes to make the UI at least as obvious as GitHub to both programmers and students, then that's a winner. Just subscribed in hopes to seeing that happen.
- ddevault 6y agoCheers :) Let me know if you come up with any questions or feedback, my door is always open at sir@cmpwn.com.