Amsterdam, The Netherlands
I like symlinks and git.
I enjoy writing low-level C code, building servers, making webapps, and learning how stuff really works.
On platforms like GitHub and GitLab it is common to send a pull/merge request to the same repo, without creating a fork. The idea is that other team members will review the code before merging it in master. When I'm working on a project together with someone else, a workflow we often use is to create a PR for changes, and that the other team member reviews it and merges it. This adds more eyes on the code and catches potential bugs.
I now understand better that this is different to the workflow used on sourcehut, where everyone has their own fork under their own user. But people will still fallback to the GitHub flow they are used to if not shown another way. So as different solution, like displaying a message on the
settings/accesspage might also be nice.
If a user visits a repo where the user has read and write permission but is not an owner, said user will be shown the clone repo button instead of the send patch button.