ML workshop day2

Harish .R — Mon, 28 Apr 2025 17:52:59 +0000

git rebase Reapplies commits on top of another base tip.

Used for cleaner history compared to merge.

bash
Copy
Edit
git rebase main
Interactive rebase (edit, squash, reorder commits):

bash
Copy
Edit
git rebase -i HEAD~5

git cherry-pick Apply a specific commit from one branch onto another.

bash
Copy
Edit
git cherry-pick

git stash Temporarily save uncommitted changes without committing them.

Save changes:

bash
Copy
Edit
git stash
Apply last stash:

bash
Copy
Edit
git stash apply
See stash list:

bash
Copy
Edit
git stash list

git reflog Shows the history of all HEAD movements.

Useful to recover lost commits.

bash
Copy
Edit
git reflog

git reset Undo commits.

Soft reset (keep changes staged):

bash
Copy
Edit
git reset --soft HEAD~1
Mixed reset (unstage changes):

bash
Copy
Edit
git reset --mixed HEAD~1
Hard reset (destroy changes):

bash
Copy
Edit
git reset --hard HEAD~1

git bisect Binary search through commits to find which commit introduced a bug.

bash
Copy
Edit
git bisect start
git bisect bad
git bisect good

git blame Show who made each change to a file.

bash
Copy
Edit
git blame

git clean Remove untracked files from the working directory.

Dry run (show what would be deleted):

bash
Copy
Edit
git clean -n
Actually delete:

bash
Copy
Edit
git clean -f

git tag Mark specific points in history as important (like releases).

Create lightweight tag:

bash
Copy
Edit
git tag v1.0
Create annotated tag:

bash
Copy
Edit
git tag -a v1.0 -m "Release version 1.0"

git submodule Manage repositories inside repositories.

Add submodule:

bash
Copy
Edit
git submodule add
Initialize submodules:

bash
Copy
Edit
git submodule init
git submodule update

git log --graph --oneline --all Visualize the repository history in a tree format.

bash
Copy
Edit
git log --graph --oneline --all

git diff Show changes between commits, branches, or working directory.

Compare working directory to staging:

bash
Copy
Edit
git diff
Compare two branches:

bash
Copy
Edit
git diff branch1..branch2

ML WORK SHOP

Harish .R — Wed, 23 Apr 2025 18:39:36 +0000

Step-by-Step Git Commands Execution:
Initialize a Git repository:
git init
Creates a new Git repository in the folder 24mcr032.

Add a file to staging area:
git add 24mcr032.txt
Adds 24MCR001.txt to the staging area.

Commit the file:
git commit -m "Added Personal Details"
Creates a commit with the message "Added Personal Details".

Check Git status:
git status
Shows that 24mcr0.txt has been modified but not staged.

View commit log:
git log
Displays the commit history (one commit at this point).

Add remote GitHub repository:
git remote add origin https://github.com/HARISH200212/24mcr032.git
Links the local repository to a remote GitHub repo.

Check current branch:
git branch
Shows the current branch is master.

Rename branch from master to main:
git branch -M main
Renames the current branch to main.

Set Git global config for email and username:
git config --global user.email "hari733733@gmail.com"
git config --global user.name "HARISH200212"
Sets your global Git identity.

Push code to remote repo for the first time:
git push -u origin main
Pushes the main branch to GitHub and sets upstream tracking.**

Then , Again We will Modify or add new file means we need to follow the same steps, like

git add .
git commit -m “message”
git push origin main

DEV Community: Harish .R

ML workshop day2

ML WORK SHOP