Git merge --no-commit tracked files without committing them -


on branch had 2 'stories', 1 wanted committed master, 1 did not.

as these changes not on feature branches, needed separate 2 somehow. used

git merge --no-commit --no-ff  

while on master. gave me staging area tweak expected, ,

git reset file  

on files relating unwanted commit. approach incorrect? result unexpected. files not added (as desired) record of them was. git tracked them removed files! when merging master tries delete uncommitted work. strange master never had of these files. extremely inconvenient, can suggest how might go 'synchronising' these changes? or perhaps better approach going forward, why --no-commit this?

i think clean way create 2 branches story1 , story2 mergebase of , master. separate a commits cherry-picking , editing/spitting commits. have 2 new branches each story separately. merge.


Comments

Popular posts from this blog

monitor web browser programmatically in Android? -

Shrink a YouTube video to responsive width -

wpf - PdfWriter.GetInstance throws System.NullReferenceException -