@fp @fluffy How do you make a patch and then test it without cloning the whole repo? Then you add the changes. Then you switch back to the webbrowser or email client to create an email where you attatch the patch file, then repeat that for every contribution

It takes all the same steps, except instead of signing into github you sign into (a likely proprietary) email service

@fp @fluffy You can actually also just fork a repo on github or gittea or gitlab or whatever and then edit it on the site if it really is something simple that you don't need to locally clone the whole repo over to test