Skip to content

Commit 1fc1ac1

Browse files
authored
git rebase usecase updated (iluwatar#246)
* Edited couple answers in the Network section * Edited Latency, Throughput and bandwidth * Edited few more answers in the Linux section * typos * git rebase usecase update
1 parent 0a3e8b6 commit 1fc1ac1

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

exercises/git/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -177,6 +177,7 @@ Using the `git rebase` command
177177

178178
<details>
179179
<summary>In what situations are you using <code>git rebase</code>?</summary><br><b>
180+
Suppose a team is working on a `feature` branch that is coming from the `main` branch of the repo. At a point, where the feature development is done, and finally we wish to merge the feature branch into the main branch without keeping the history of the commits made in the feature branch, a `git rebase` will be helpful.
180181
</b></details>
181182

182183
<details>

0 commit comments

Comments
 (0)