On GitHub if you click the fork button instaid of the template button during setup you get the option to commit either to your own copy or as a PR to the upstream repo, forks are always public though
Discussion
Ah ok. So if I think something is a fix I would do a PR, and if it’s just my customization it would be a commit to my fork. Would future updates to the upstream repo be applied to my fork via a merge? Also, any drawbacks on being public?
Yes but it will get messy having own customisation & fixes coming from the same repo so you kind of end up submitting a file with both things in it. So a clean fork or synced fork is preferred to commit fixes from. No draw backs from setting the repo public unless you make custom changes that you would rather not share yet✌️