9 Commits

Author SHA1 Message Date
7a13b039d5 add new word 2025-11-07 13:05:17 +05:30
d46de89da9 add one number 2025-11-07 12:11:40 +05:30
f08ba6ad8e add the words 2025-11-07 11:56:20 +05:30
8642962101 mareg the file 2025-09-11 10:31:04 +05:30
559cf18b71 add file readme.md 2025-09-04 10:20:41 +05:30
dea0695eb0 gitignore file 2025-08-30 11:52:01 +05:30
2b4e92d9d1 bug sheet file added 2025-08-23 12:26:20 +05:30
43741c73f5 add the file 2025-08-23 12:16:15 +05:30
2535add914 new file 2025-08-23 12:07:18 +05:30
25 changed files with 6 additions and 62 deletions

2
.gitignore vendored
View File

@@ -1 +1 @@
secret.txt
secret.txt

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 23 KiB

View File

@@ -1,4 +1,4 @@
### Repository Creation
### Step 1: Repository Creation
I created a new repository inside the **Git-Training-Hub** organization on Git Comorin.
The repository name is `git-practice-muralikrishnan.rajamuni`
@@ -6,57 +6,3 @@ It was created empty (no README, no .gitignore, no license).
### Screenshot:
![Repository Creation](GIT_ASSIGNMENT.png)
### Step 1: What is Git and Version Control
Version Control is a system that records changes to files over time.
Git is the most popular Version Control System (VCS).
Its distributed, meaning every developer has a full copy of the project history (not just files).
### Step 2: Installing Git & Configuring User Info
![Repository Creation](git_version.png)
![Repository Creation](git_config.png)
### Step 3: Initializing a Repository
![Repository Creation](git_init.png)
### step 4: Working Directory, Staging, and Commits:
![Repository Creation](git_add.png)
![Repository Creation](git_commit.png)
![Repository Creation](git_status.png)
### Step 5: Viewing Commit Logs & Diffs:
![Repository Creation](git_diff.png)
![Repository Creation](git_log.png)
![Repository Creation](git_log_oneline.png)
### Step 6 : Creating & Switching Branches:
![Repository Creation](git_branch.png)
![Repository Creation](git_checkout.png)
### Step 7: Cloning a Remote Repository:
![Repository Creation](git_cloned.png)
### Step 8: Adding & Managing Remotes
![Repository Creation](git_remoteadd.png)
![Repository Creation](git_remote.png)
### Step 9: Pushing
![Repository Creation](git_push.png)
### Step 10: Pull
![Repository Creation](git_pull.png)
### Step 11: Ignoring Files with .gitignore:
![Repository Creation](.gitignore.png)
### Viewing File History
![Repository Creation](gitlog-p.png)
![Repository Creation](gitlog--oneline.png)
### Viewing File History with Blame
![Repository Creation](gitblame.png)
![Repository Creation](gitblame-L.png)
![Repository Creation](gitblame-e.png)

0
README.md Normal file
View File

View File

Before

Width:  |  Height:  |  Size: 25 KiB

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 61 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 33 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 33 KiB

View File

Before

Width:  |  Height:  |  Size: 9.9 KiB

After

Width:  |  Height:  |  Size: 9.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

View File

@@ -1,6 +1,2 @@
# the text file
# murali krishnan
#Version Control is a system that records changes to files over time.
Its distributed, meaning every developer has a full copy of the project history (not just files).
Hello Mark
hello mark
# murali krishnan R

View File

@@ -1 +0,0 @@
# secret text create

View File

@@ -1 +1,4 @@
# bug sheet file added
The git merge command in Git is used to integrate changes from one branch into another.
This process combines the independent lines of development created by git branch and
integrates them into a single, unified branch

Binary file not shown.

Before

Width:  |  Height:  |  Size: 25 KiB