title: Best workflow on a forked project, which will never merge back into original, but to get updates?
body: <p>I'm new to git, and I have a project that I've forked from the original Open Source on Github.</p>
  <p>I'm customising the code for my own project, and will never merge back into the original.</p>
  <p>I want to benefit from bug fixes and updates on the original.</p>
  <p>What approach should I take without having to resolve the same conflicts over and over again? Should I try to avoid modifying the original code modules and import them into new modules? (I'm working in python).</p>
  <p>Is there a particular approaching to branching that would help?</p>