假设我的存储库的主分支如下所示:
* commit 75e259944814a102d6362eaf42fd4ff09d839865
|
| Bad commit
|
* commit 0307a5c4e623c584898c44d243a50bb02c91aa9e
|
| Good commit 1.
|
* commit 98ef0e69e3e5cd51ff5e24c1df616703272c5a79
|
| Good commit 1.
|
错误的提交已被推送到中央存储库并分发。我想继续上一次好的提交的历史。完成后,我希望历史看起来像
* commit 0626f793ff7ba847e7663fe88de6c6a2d597dc73
|
| Continuing development.
|
| * commit 75e259944814a102d6362eaf42fd4ff09d839865
| |
| | Bad commit
| |
| |
| |
* | commit 0307a5c4e623c584898c44d243a50bb02c91aa9e
|/
| Good commit 2.
|
|
|
* commit 98ef0e69e3e5cd51ff5e24c1df616703272c5a79
|
| Good commit 1.
|
也就是说,开发从最后一个“好”提交继续。即使“错误”提交已在开发人员之间分发,我能否安全地实现这一目标?