My current state:
- Created and commited a JS development environment - call it Master A.
- Continued to write new code on Master A, yet didn't commit any of the new code yet.
Expected state:
- I would like my initial commit to Master B to include all the new and uncommitted written code from Master A + Include all commits of Master A.
- I would like to have Master A available and re-usable to use it as a boilerplate for future JS environment projects.
I am looking for a stenciled workflow solution, not a one time solution for this issue.
Not looking to create new branches on Master A as solution, please. I would like to keep Master A organic for others to pull and benefit with no clutter/branches.
Thanks,
Buddy