Using flask-base as a base for a new project? about flask-base HOT 5 CLOSED

Great question. What I have done, which may not be the best approach, is set two remotes in the downstream project named origin and flask-base. origin points to your project's repository and flask-base points to this repository. This way, you can cherry-pick any flask-base commits you want (just git fetch first).

from flask-base.

Oh, and I don't think submodules is the right solution to the problem. From what I understand, they require that the submodule be kept in a subdirectory. Plus, once you fork off of flask-base, you may make changes which conflict with flask-base changes, or you may not want to include all upstream changes.

from flask-base.

True, Ideally you want to be able to pull updates from flask-base and not commit to it. Commits for fixes could be sent separately.

from flask-base.

Right. So the workflow could be something like this.

1. Do work normally using feature branches, pull requests, etc.
2. Occasionally make a feature branch where you can cherry-pick specific flask-base changes.
3. Make a pull request for those changes like you normally would.

from flask-base.

Closing issue. Feel free to reopen/create a new issue if you have further questions.

from flask-base.