branch - Untracked files between branches in Git -


I'm looking around here to seek an answer and it seems that I have to work with Git branches.

I have my Master branch and I have created a facility branch named "code> profile", where I am doing some specific work on profile for profile While working, I changed the 5 or 6 files and added 5 or 6 new files. To recover a quick bug I had to switch back to the Master branch and all the new files And the revised files were viewed, wherever I came along It is understandable that this is not because GIT Master is not intended to remove unencrypted files from the branch and bring them back to my profile branch, in fact, untrek but What are the changes in the existing files, why they are showing in the Master branch.

What is the best practice here I am not ready to make changes locally. Would I just hide all these changes, switch to master , make small improvements, switch back to profiles

any Also help is made of its purgery. Thanks

"I am not ready to make changes locally."

Commitment in GIT is local things that can be canceled, can be done again and can be done again. It only happens when you are committed to anywhere that you have to pay attention.

Plus, commands are visible to local devices like gitk , and may be different from them and may be leaked on other commitments etc. It's a very powerful tool to learn how to use it.

I do this so often:

  git add If I think that I may be obstructed then the current work is to hide everything in the tree - git commit -a -m 'wip'  

If I make some more changes, So I use it:

  git add Git commit --amend  

Update in-place to update my "Yip" When I'm finally ready to commit real, I just:

< Ex> git reset - soft HEAD ~; GIT reset

And now I can carefully control what the final commitment will be.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -