• Git----分支管理之bug分支04


    ---恢复内容开始---

      软件开发中,bug就像家常便饭一样,有了bug就需要修复,在Git中,由于分支是如此强大,所以,每个bug都可以通过一个临时分支来修复,修复后,合并分支,然后将临时分支删除。

      当你接到一个修复一个代号101的bug任务时,很自然地,你想创建一个分支issue-101来修复它,但是,等等,当前正在dev上进行的工作还没有提交:

    $ git status
    On branch master
    Your branch is up to date with 'origin/master'.

    Changes to be committed:
    (use "git reset HEAD <file>..." to unstage)

    new file: hello.py

    Changes not staged for commit:
    (use "git add <file>..." to update what will be committed)
    (use "git checkout -- <file>..." to discard changes in working directory)

    modified: readme.txt

       并不是你不想提交,而是工作只进行到一半,还没发提交,预计完成还需1天时间,但是,必须在两个小时之内修复该bug,怎么办?

      幸好,Git还提供了一个stash功能,可以把当前工作现场“储藏”起来,等以后恢复现场后继续工作

    $ git stash
    Saved working directory and index state WIP on dev: 45e3302 add merge

    现在,用git status查看工作区,就是干净的(除非有没有被Git管理的文件),因此可以放心的创建分支来修复bug。

    $ git status
    On branch dev
    nothing to commit, working tree clean

    首先确定要在哪个分支上修复bug,假定需要在master分支上修复,就从master创建临时分支:

    $ git checkout master
    Switched to branch 'master'
    Your branch is up to date with 'origin/master'.

    $ git checkout -b issue-101
    Switched to a new branch 'issue-101'

    现在修复bug,需要把readme.txt里面的内容“Git is software...”改为“Git is a free software....”然后提交

    $ git add readme.txt

    $ git commit -m "fix bug 101"
    [issue-101 27c08c6] fix bug 101
    1 file changed, 1 insertion(+), 1 deletion(-)

    修复完成以后,切换到master分支,并合并完成,最后删除issue-101

    $ git checkout master
    Switched to branch 'master'
    Your branch is up to date with 'origin/master'.

    $ git merge --no-ff -m "merged bug fix 101" issue-101
    Merge made by the 'recursive' strategy.
    readme.txt | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    太棒了,原计划两个小时的bug修复只花了五分钟,现在,是时候接着回到dev分支干活了

    $ git checkout dev
    Switched to branch 'dev'

    $ git status
    On branch dev
    nothing to commit, working tree clean

    工作区是干净的,刚才的工作现场存到哪里去了?用git stash list命令看看:

    $ git stash list
    stash@{0}: WIP on dev: 45e3302 add merge

    工作现场还在,Git把stash内容存到某个地方了,但是需要恢复一下,有两个办法:

    一是用git stash apply恢复,但是恢复后,stash内容并不删除,你需要用git stash drop来删除;

    另一种方式是用git stash pop,恢复的同时把stash内容也删了。

    $ git stash pop
    On branch dev
    Changes to be committed:
    (use "git reset HEAD <file>..." to unstage)

    new file: hello.py

    Changes not staged for commit:
    (use "git add <file>..." to update what will be committed)
    (use "git checkout -- <file>..." to discard changes in working directory)

    modified: readme.txt

    Dropped refs/stash@{0} (b0d65dce977ac8b90006982914b08c161363c942)

    再用git stash list查看,就看不到任何stash内容了:

    $ git stash list

    你可以多次stash,恢复的时候,先用git stash list查看,然后恢复指定的stash,用命令:

    $git stash apply stash@{0}

     摘抄自:

    https://www.liaoxuefeng.com/wiki/0013739516305929606dd18361248578c67b8067c8c017b000/00137602359178794d966923e5c4134bc8bf98dfb03aea3000

  • 相关阅读:
    The 2019 China Collegiate Programming Contest Harbin Site A
    牛客练习赛15
    Wannafly挑战赛13-C
    Wannafly挑战赛13-D
    Subsequence Counting
    Minimize the error
    Educational Codeforces Round 42 (Rated for Div. 2)
    K-th Number
    Wannafly挑战赛13-E
    Minimum spanning tree for each edge
  • 原文地址:https://www.cnblogs.com/cxq0017/p/9729002.html
Copyright © 2020-2023  润新知