Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • I'm trying the Git upstream method. I made a copy of the repo and set an upstream remote pointing back to the original. Then I just merge upstream/master into the copy's master. So it seems no different than normal merging. Commented Nov 1, 2019 at 0:49
  • @Ryan exactly; this is why it is not a good idea that user just changes the code as desired: sooner or later merge conflicts will occur. Therefore, design the code so as to avoid that customer wants to change it in his fork (relying on language semantics rather that git’s text processing). This is safe, and it’s the underlying philosophy to a lot of package managers. If changes can really not be avoided in some file, then, at least isolate the changeable parts in clearly idenfified sections of your source file and provide instructions on how to solve the merge conflicts. Commented Nov 1, 2019 at 9:09