GIT Branch

When a stable version is released, a new function point comes. At this time, we need to make a branch and then

develop it. Create a new branch002 on the previous branch001 and
add the file test001.
Switch to the previous branch001 and
find that test001 is still there It should be gone (or my purpose is that the current modification does not affect the previous branch). The

solution is to switch to branch002, commit your code (you may not push, here are all commits to the current branch branch002, which has nothing to do with branch001), and then If you switch to branch001, you will not see test001. Create a new branch002


on the previous branch001 and
modify the previous file
. Switch to the previous branch001 and
prompt
you . Either merge or commit your code before switching branches, commit your code (You may not push, here are all commits to the current branch branch002, which has nothing to do with branch001), and then switch to branch001 and test001 will not be seen