Let's say that I want to contribute to
thislib, which is a Python library that is available as a Git repository. Several applications, such as
thislib_app utilize this library, and I want to contribute to the
thislib and see how my optimizations work out for
thislib_app (we can say that
thislib_app is like one big unit test).
Here's my workflow:
- Clone the
- Create a
thislib_app. Oh no! Something breaks, but it's
- Go inside
lib_env/local/lib/python/site-packages/thislib/x.pyand make necessary changes
- Test again. It works!
Now in order to make these changes known to maintainers, I must clone a fork of
thislib's repository, copy OVER the changes I've made in the
virtualenv to my development branch, and make a PR. If I decide to make more optimizations / changes, I would have to repeat this copy process over again.
What can I do to ensure an efficient workflow where I do not have to move around my changes and can get a PR up immediately?