Compare commits
10 Commits
main
...
feature/te
Author | SHA1 | Date | |
---|---|---|---|
6d7c4ec657 | |||
dc8ae9051e | |||
e9870f64f7 | |||
9c3547a940 | |||
58880219ea | |||
2745965e15 | |||
cba5dc492d | |||
071d2cf8a6 | |||
46c4db4c17 | |||
5c23bb7dcb |
1
.gitignore
vendored
@ -1 +0,0 @@
|
||||
.ignore.txt
|
36
ASSIGNMENT-04-09-2025.md
Normal file
@ -0,0 +1,36 @@
|
||||
## Part 1: Viewing File History
|
||||
|
||||

|
||||

|
||||

|
||||
## How many commits modified this file?
|
||||
7 commits
|
||||
|
||||
## What differences do you see when adding the -p option?
|
||||
Shows detailed changes for each commit in the file.
|
||||
|
||||
## Part 2: Viewing File History with Blame
|
||||

|
||||

|
||||

|
||||
|
||||
## Who changed each line of the file?
|
||||
Ajishini, Solomon
|
||||
|
||||
## How does -L help when the file is large?
|
||||
To view the history of specific lines in a file.
|
||||
|
||||
## What extra information does -e provide?
|
||||
|
||||
To get the email id of the user who made the chages in the file.
|
||||
|
||||
## Part 3: Merging Branches
|
||||
|
||||

|
||||
|
||||
## Did Git perform a fast-forward merge or a 3-way merge?
|
||||
Merge conflict
|
||||
|
||||
## What does git log --graph --oneline --all show after the merge?
|
||||

|
||||
|
@ -3,27 +3,3 @@ Step 1 : Create new empty repository
|
||||
- Created a new repository named as git-practice-Ajishini
|
||||
- Created with no README, no .gitignore and no license
|
||||
- 
|
||||
1. Checking Git Version
|
||||
- 
|
||||
2. Checking Git Status
|
||||
- 
|
||||
3. Adding Files to Staging
|
||||
- 
|
||||
4. Viewing Commit History
|
||||
- 
|
||||
5. Compact History (Oneline)
|
||||
- 
|
||||
6. Visual History (Graph)
|
||||
- 
|
||||
7. Checking Differences
|
||||
- 
|
||||
8. Comparing Two Commits
|
||||
- 
|
||||
9. Exploring Branches
|
||||
- 
|
||||
10. Cloning a Repository
|
||||
- 
|
||||
11. Pulling the Code
|
||||
- 
|
||||
12. Using gitignore
|
||||
- 
|
BIN
cloned-repo.png
Before Width: | Height: | Size: 53 KiB |
7
example.txt
Normal file
@ -0,0 +1,7 @@
|
||||
New file created
|
||||
Added to git
|
||||
Commit message
|
||||
check the status
|
||||
Switch to new branch
|
||||
Check log
|
||||
Added new line in the feature/testcase branch
|
BIN
git blame -L 1,5 example.txt.png
Normal file
After Width: | Height: | Size: 21 KiB |
BIN
git blame -e example.txt.png
Normal file
After Width: | Height: | Size: 31 KiB |
BIN
git blame example.txt.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
git log --example.png
Normal file
After Width: | Height: | Size: 36 KiB |
BIN
git log --graph --oneline --all.png
Normal file
After Width: | Height: | Size: 98 KiB |
BIN
git log --oneline -- example.txt.png
Normal file
After Width: | Height: | Size: 36 KiB |
BIN
git log -p -- example.txt.png
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
git merge.png
Normal file
After Width: | Height: | Size: 52 KiB |
Before Width: | Height: | Size: 26 KiB |
BIN
git_commit.png
Before Width: | Height: | Size: 34 KiB |
BIN
git_diff.png
Before Width: | Height: | Size: 24 KiB |
BIN
git_ignore.png
Before Width: | Height: | Size: 32 KiB |
Before Width: | Height: | Size: 22 KiB |
BIN
git_log.png
Before Width: | Height: | Size: 40 KiB |
BIN
git_pull.png
Before Width: | Height: | Size: 29 KiB |
BIN
git_version.png
Before Width: | Height: | Size: 21 KiB |
@ -1 +1 @@
|
||||
Create new text file
|
||||
Create new branch
|
@ -1,7 +0,0 @@
|
||||
- Created readme.md in a repo and renamed it to README.md
|
||||
- 
|
||||
- Git didn’t show changes because windows system is case-insensitive
|
||||
- Fixed it using:
|
||||
`git mv -f readme.md README.md`
|
||||
`git commit -m "Rename readme.md to README.md"`
|
||||
- Reason: Git is case-sensitive, but case-insensitive filesystems treat both names as the same
|
BIN
readme.png
Before Width: | Height: | Size: 57 KiB |
BIN
repo_edit.png
Before Width: | Height: | Size: 14 KiB |
@ -1 +0,0 @@
|
||||
this is a txt file
|