EXP-2
Tasks on Exploring GitHub
Task-1
create a personal GitHub profile README that showcases your
identity, skills, and activity in a creative, professional, and
technically impressive way using Markdown.
Steps to Do the Task
Step 1: Create the Special Repository
Go to: https://github.com/new
Repository name = Your GitHub username (exact match)
👉 For example, if your username is renukacsit, repo name should also
be renukacsit
Keep it Public
Check ✅ "Initialize this repository with a README"
Click Create repository
Step 2: Edit Your README.md
Now that the repository is created:
Click on the README.md file in the repo
Click the ✏️pencil icon to edit
Paste your custom Markdown content (see below)
Sample README Template
# 👋 Hi there, I'm Renuka!- 💻 I’m passionate about Full Stack Development
& Cybersecurity- 🌱 Currently learning: Spring Boot, MongoDB, and GitHub
Actions- 💡 Fun Fact: I once debugged a 50-line error just by adding a
semicolon 😂
## Skills & Tools
## 📈 GitHub Stats
## 📫 Connect with Me- ✉️Email:
[email protected] 🔗 LinkedIn:
[Renuka Profile](https://linkedin.com/in/renuka-example)
Step 3: Use Shields.io for Custom Badges
Visit: https://shields.io
Choose a style (e.g., “for-the-badge”)
Pick logo and color
Copy the Markdown code and paste it into your README
Fill in the fields:
Label = What the badge says on the left (e.g., Java)
Message = What it says on the right (e.g., Advanced)
Color = Pick a color (e.g., green, blue, orange, red, or HEX like
#4CAF50)
Style = Choose from:
flat
flat-square
for-the-badge ← recommended for bold display
plastic
Logo (Optional) = Add logos like github, java, spring, python, mongodb,
etc.
Step 4: Add GitHub Stats (Optional but Cool)
Paste the following lines (replace with your username):
Step 5: Save and View
Scroll down and click Commit changes
Now go to your GitHub profile page
You’ll see your custom README displayed at the top
Task-2:
Code Snippet Library Repo:Create a personal or collaborative
GitHub repository to store and organize your favorite code
snippets in multiple programming languages.
Create a repo called code-snippets
Each student creates .py, .java, .js files with their favorite code
snippets
Use README.md to index and link all the files
Optional: Invite classmates to contribute snippets (collaborative)
Instructions:
1.Repository Setup:
Create a GitHub repository named: code-snippets.
2. Add Code Files:
Create code snippet files in your preferred languages:
Python → loops.py, recursion.py
Java → OOPDemo.java, Sorting.java
JavaScript → dom-manipulation.js, fetchAPI.js
Each file should contain useful, reusable code with comments.
3. Create a README.md:
Use Markdown to organize and index the code files.
# Code Snippet Library
## 🐍 Python Snippets
- [Loops in Python](loops.py)
- [Recursion Example](recursion.py)
## ☕ Java Snippets
- [OOP Demo](OOPDemo.java)
- [Sorting Techniques](Sorting.java)
## 🌐 JavaScript Snippets
- [DOM Manipulation](dom-manipulation.js)
- [Fetch API Example](fetchAPI.js)
Example:
4.Bonus – Collaboration:
Invite classmates as collaborators using the Settings > Collaborators
tab.
Use pull requests to review and merge contributions.
EXP-3:
Task:Git Branching Story Project: “A Tale in Branches”
USe Git branches to create a collaborative or personal story. Each
branch represents a chapter, and finally, they merge all into a
single book.html file.
Instructions
🧱 Step 1: Project Setup
Open Git Bash.
Create a new folder and initialize a Git repo:
bash
mkdir story-branches
cd story-branches
git init
Create a basic HTML template file:
echo "<html><body><h1>My Storybook</h1></body></html>"
>book.html
git add book.html
git commit -m "Initial story template"
🌿 Step 2: Create Chapter Branches
Create a branch for each chapter:
git checkout -b chapter1
Edit book.html and insert your first chapter inside <body>:
<h2>Chapter 1: The Mysterious Forest</h2><p>Once upon a time,
deep in the forest...</p>
git add book.html
git commit -m "Add Chapter 1"
Repeat steps for:
git checkout main
git checkout -b chapter2
<h2>Chapter 2: The Hidden Cave</h2><p>The hero stumbled
upon a cave glowing with strange light...</p>
Commit as before.
You can create more chapters this way (e.g., chapter3, chapter4, etc.).
🔄 Step 3: Merge Chapters into Main Story
Return to main:
git checkout main
Merge each chapter one at a time:
git merge chapter1
git merge chapter2
⚠️If merge conflicts occur (if multiple branches edit the same line), resolve
them using any code editor or via Git Bash:
nano book.html # resolve conflicts manually
git add book.html
git commit -m "Resolve merge conflict"
🧾 Step 4: Final Story
Open book.html in a browser:
start book.html # On Windows# OR
xdg-open book.html # On Linux
You’ll see all chapters combined into one full HTML page!
