DEV Community: THANUSRI

Advanced Git commands

THANUSRI — Mon, 28 Apr 2025 16:28:11 +0000

git diff - See changes between commits
git log - See commit history
git clone - Remote repo → Local
git fork - Create copy of repo under your account
git pull - Remote latest changes → Local
git push - Local commits → Remote
git blame - Who changed which line
git merge - Combine branches
git branch - Displays current branch
.gitignore - Skip tracking files

Creating a new branch and adding the Dockerfile

THANUSRI — Mon, 28 Apr 2025 16:00:32 +0000

====REPO LINK==== https://github.com/thanusri7012/24MCR115

PUSH THE DOCKERFILE INTO GITHUB :

# Step 1: Create and switch to a new feature branch from 'main'

git checkout main -b feature1-24MCR115

This creates a new branch called feature1-24MCR115 and switches to it. Always create a new branch for a feature to keep main clean.

# Step 2: Check branches

git branch

This lists all local branches. The * indicates your current branch.

# Step 3: Check current file changes

git status

This shows:
You're on branch feature1-24MCR115
You have untracked files: Dockerfile, some images (d1.jpg, d2.jpg, etc.), and a .webp file
These are not staged yet.

# Step 4: Add all files to staging area

git add .

This adds all untracked and modified files in the current directory recursively to staging. It's shorthand for git add for each file.

✅ Git Commit & Push Workflow

Step 1: Committing the Changes

git commit -m "Added docker file successfully"

This command commits the staged changes with a message describing the update.

Output:

[feature1–24MCR115 f3d70da] Added docker file successfully

Indicates a successful commit with the commit hash.

Shows that Dockerfile was created and 18 lines were added.

Step 2: Pushing the Feature Branch to Remote

git push origin feature1–24MCR115

This pushes your local branch feature1–24MCR115 to the remote repository.

Output:

Git compresses and uploads your commits.

Confirms successful push:

Dockerize a Python ML Model using SVM

THANUSRI — Mon, 28 Apr 2025 15:36:55 +0000

DOCKER COMMANDS

1.Check Docker version :

docker --version

Can check the docker version.

2.Create a Dockerfile in your project :

3.Docker Login :

docker login

4.Build Docker image :

docker build -t thanusri7012/24mcr1152:latest .

5.List Docker images :

docker images

6.Push Docker image to DockerHub :

docker push thanusri7012/24mcr1152

7.Open Docker Desktop to view images and containers :

8.Verify the Docker image and running container in Docker Desktop (GUI):

Dockerize a Python ML Model

THANUSRI — Fri, 25 Apr 2025 15:27:18 +0000

DOCKER COMMANDS

1.Check Docker version :

docker --version

Can check the docker version.

2.Create a Dockerfile in your project :

3.Docker Login :

docker login

Enter the login id and password

4.Build Docker image :

docker build -t thanusri7012/24mcr115:latest .

5.List Docker images :

docker images

6.Push Docker image to DockerHub :

docker push thanusri7012/24mcr115

7.Open Docker Desktop to view images and containers :

8.Run the Docker container :

9.Verify the Docker image and running container in Docker Desktop (GUI)

PUSH THE DOCKERFILE INTO GITHUB :

# Step 1: Create and switch to a new feature branch from 'main'

git checkout main -b feature1-24MCR115

This creates a new branch called feature1-24MCR115 and switches to it. Always create a new branch for a feature to keep main clean.

# Step 2: Check branches

git branch

This lists all local branches. The * indicates your current branch.

# Step 3: Check current file changes

git status

This shows:
You're on branch feature1-24MCR115
You have untracked files: Dockerfile, some images (d1.jpg, d2.jpg, etc.), and a .webp file
These are not staged yet.

# Step 4: Add all files to staging area

git add .

This adds all untracked and modified files in the current directory recursively to staging. It's shorthand for git add for each file.

✅ Git Commit & Push Workflow

Step 1: Committing the Changes

git commit -m "Added docker file successfully"

This command commits the staged changes with a message describing the update.

Output:

[feature1–24MCR115 f3d70da] Added docker file successfully

Indicates a successful commit with the commit hash.

Shows that Dockerfile was created and 18 lines were added.

Step 2: Pushing the Feature Branch to Remote

git push origin feature1–24MCR115

This pushes your local branch feature1–24MCR115 to the remote repository.

Output:

Git compresses and uploads your commits.

Confirms successful push:

Machine Learning with Iris Dataset – Logistic Regression Model

THANUSRI — Thu, 24 Apr 2025 14:39:53 +0000

📌 What I Did:

Loaded and explored the Iris.csv dataset.
Plotted histograms and density plots for visual exploration of feature distributions.
Split the data into training and testing sets.
Trained a Logistic Regression model to classify iris species based on flower measurements.
Evaluated the model’s accuracy on unseen data.
Saved the trained model as logistic_model.pkl for reuse or deployment.

🧠 ML Libraries Used & How I Installed Them:

✅ Pandas

pip install pandas

For easy data manipulation and analysis.

✅ Scikit-learn

pip install scikit-learn

The ML powerhouse! Used for splitting data, training the model, and evaluation.

✅ Matplotlib

pip install matplotlib

For visualizing data with plots and charts.

Snippet :

Output :

Histogram :

Density_Plots :

GitHub Repository :

✅ First Push Attempt (Everything up-to-date):

git push origin feature-24MCR115

Everything up-to-date
This means you had already pushed the feature-24MCR115 branch earlier, and no new commits were made since then.

✅ Staging and Committing New Files :

git status
git add .
git add .gitignore hello_world_ml.py logistic_model.pkl
git commit -m "[feature-24MCR115 b890daa] Added ML model, script, and gitignore"

You staged all files using git add ..
You explicitly staged .gitignore, hello_world_ml.py, and logistic_model.pkl again (not harmful, just redundant since they were already added with git add .).
The commit was successfully created and shows the files added:
.gitignore
hello_world_ml.py
logistic_model.pkl

GITHUB REPOSITORY SETUP

THANUSRI — Thu, 24 Apr 2025 03:09:52 +0000

Step 1: Initialize Git

git init

This creates a new Git repository in the current directory.

Step 2: Add Files to Staging Area

git add filename

This stages all the files (in my case, the 24MCR115 file) for commit.

Step 3: Commit Changes

git commit -m "Initial commit with 24MCR115 details"

This commits the staged files with a message.

Step 4: Check Repository Status

git status

To see what’s changed and what’s staged/untracked.

Step 5: View Commit History

git log

To view all commits made to the repository.

Step 6: Create or Rename Branch

git branch
git branch -M main

Check current branches and rename the branch to main.

Step 7: Configure Git Identity

git config --global user.name "Your Name"
git config --global user.email "your.email@example.com"

Set your GitHub username and email.

Step 8: Link to Remote Repository

git remote add origin https://github.com/your-username/24MCR115.git

This connects your local repo to the GitHub repository.

Step 9: Push to GitHub

git push -u origin main

Push your committed changes to GitHub under the main branch.