Week 2 Day 4: GitHub basics and repository management
This commit is contained in:
32
Week-2/Day-4/Readme.md
Normal file
32
Week-2/Day-4/Readme.md
Normal file
@@ -0,0 +1,32 @@
|
|||||||
|
# Week 2 – Day 4
|
||||||
|
## GitHub Basics and Repository Management
|
||||||
|
|
||||||
|
### Date
|
||||||
|
25 December 2025
|
||||||
|
|
||||||
|
### Objective
|
||||||
|
To understand GitHub fundamentals, repository creation, and basic project structure using GitHub interface.
|
||||||
|
|
||||||
|
### Topics Covered
|
||||||
|
- GitHub overview
|
||||||
|
- Repository creation
|
||||||
|
- README file importance
|
||||||
|
- GitHub Flow basics
|
||||||
|
|
||||||
|
### Activities Performed
|
||||||
|
- Created a sample repository.
|
||||||
|
- Explored GitHub interface and repository settings.
|
||||||
|
- Studied GitHub Flow documentation.
|
||||||
|
- Understood role of README files.
|
||||||
|
|
||||||
|
### Tools & Technologies Used
|
||||||
|
- GitHub
|
||||||
|
- Markdown
|
||||||
|
|
||||||
|
### Learning Outcomes
|
||||||
|
- Learned how repositories are structured.
|
||||||
|
- Understood the importance of version control.
|
||||||
|
- Gained confidence using GitHub UI.
|
||||||
|
|
||||||
|
### Status
|
||||||
|
Completed
|
||||||
33
Week-2/Day-4/github-basics.md
Normal file
33
Week-2/Day-4/github-basics.md
Normal file
@@ -0,0 +1,33 @@
|
|||||||
|
## Introduction to GitHub
|
||||||
|
GitHub is a cloud-based platform used to host Git repositories and manage version control. It enables developers to collaborate, track changes, and manage code efficiently.
|
||||||
|
|
||||||
|
## Key Concepts Learned
|
||||||
|
### Repository
|
||||||
|
A repository is a container for a project.
|
||||||
|
Stores files, folders, and version history.
|
||||||
|
Can be public or private.
|
||||||
|
Usually contains a README.md file describing the project.
|
||||||
|
|
||||||
|
### README File
|
||||||
|
Written in Markdown.
|
||||||
|
Explains project purpose, usage, and structure.
|
||||||
|
First file users see when opening a repository.
|
||||||
|
|
||||||
|
### GitHub Interface Basics
|
||||||
|
Code tab → View project files
|
||||||
|
Pull Requests tab → Manage contributions
|
||||||
|
Branches dropdown → Switch between versions
|
||||||
|
|
||||||
|
### GitHub Flow Overview
|
||||||
|
GitHub Flow is a lightweight workflow used to manage changes:
|
||||||
|
Create a repository
|
||||||
|
Create a branch
|
||||||
|
Make changes and commit
|
||||||
|
Open a pull request
|
||||||
|
Merge changes
|
||||||
|
|
||||||
|
### Importance of Version Control
|
||||||
|
Tracks changes over time
|
||||||
|
Prevents data loss
|
||||||
|
Enables team collaboration
|
||||||
|
Maintains clean project history
|
||||||
Reference in New Issue
Block a user