01-11-2018, 07:27 AM
>you make a change which is only for your project, you commit it and continue
... should't I put that in another branch than master (local) - like a branch dev_local?
otherwise, if I do changes like:
change 1 (global)
change 2 (local only, no general interest to public)
change3 (globl)
and send a pull request, my local change will be in that pull request as well?
I think I would keep my local master in sync with upstream master and occasionally merge that into my local branch dev_local.
Locally, I would deploy from dev_local. Now I can insert code totally unrelated to global corebos development.
Or am I wrong in this?
... should't I put that in another branch than master (local) - like a branch dev_local?
otherwise, if I do changes like:
change 1 (global)
change 2 (local only, no general interest to public)
change3 (globl)
and send a pull request, my local change will be in that pull request as well?
I think I would keep my local master in sync with upstream master and occasionally merge that into my local branch dev_local.
Locally, I would deploy from dev_local. Now I can insert code totally unrelated to global corebos development.
Or am I wrong in this?