Skip to content

Commit 43385f3

Browse files
⛙ day 30 - merged popped stash
1 parent d208656 commit 43385f3

File tree

1 file changed

+54
-0
lines changed

1 file changed

+54
-0
lines changed

Day 30/README.md

+54
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Day 30
2+
3+
Today we will learn to merged popped stash.
4+
5+
## Problem Statement:
6+
7+
When you want to reapply your changes but you already continued working on your file, you might get a merge conflict! Let's practise this situation.
8+
9+
Pop the changes from the stash with `git stash pop` and resolve the merge conflict. Commit the resolved changes and clear the stash stack afterwards.
10+
11+
### Files:
12+
- recipe
13+
14+
### Questions:
15+
- Did you resolve the confict and commit?
16+
- Did you clear stash stack?
17+
18+
19+
<div align="center">
20+
<img src="https://github.com/ArnabKumarRoy02/Learn-git/assets/86621483/2f7b1795-c0d9-431d-9da6-62777d07e4cf" width=450>
21+
<p>Description of the problem.</p>
22+
</div>
23+
24+
## Solution:
25+
26+
1. Check out the stash list.
27+
```bash
28+
git stash list
29+
```
30+
31+
2. Pop the stash item.
32+
```bash
33+
git stash pop
34+
```
35+
36+
3. Edit the files necessary to commit.
37+
```bash
38+
# Edit files
39+
nvim recipe
40+
41+
# Add the file and commit it
42+
git add .
43+
git commit -m "updated"
44+
```
45+
46+
4. Clear out the stash list.
47+
```bash
48+
git stash clear
49+
```
50+
51+
<div align="center">
52+
<img src="https://github.com/ArnabKumarRoy02/Learn-git/assets/86621483/8b78fce3-9101-45f6-aeb7-d63760fe89d0" width=450>
53+
<p>Description of the solution.</p>
54+
</div>

0 commit comments

Comments
 (0)