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?

Reply to this note

Please Login to reply.

Discussion

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✌️

Oh yeah that makes sense. I guess the only thing would be getting any updates from the upstream repo, but I can cross that bridge when I get there. Mind if I DM you if I have more questions?

Feel free to shoot em when you got em ✌️