Week 2 Day 5: GitHub branching and pull request workflow

Week-2/Day-5/Readme.md

@@ -0,0 +1,32 @@
+# Week 2 – Day 5
+## GitHub Branching and Pull Requests
+
+### Date
+26 December 2025
+
+### Objective
+To learn how branching, committing, and pull requests work in GitHub using GitHub Flow.
+
+### Topics Covered
+- Branch creation
+- Making commits
+- Pull request workflow
+- Merging changes
+
+### Activities Performed
+- Created a new branch from main.
+- Edited README file in the branch.
+- Committed changes with meaningful messages.
+- Opened and merged a pull request.
+
+### Tools & Technologies Used
+- GitHub
+- Markdown
+
+### Learning Outcomes
+- Understood GitHub collaboration workflow.
+- Learned how to safely merge changes.
+- Gained practical experience with pull requests.
+
+### Status
+Completed

Week-2/Day-5/github-notes.md

@@ -0,0 +1,34 @@
+## Branching in GitHub
+
+### What is a Branch?
+- A branch is a copy of the main codebase.
+- Allows working on features without affecting main branch.
+- Default branch is usually called main.
+
+### Creating and Using Branches
+- Branches are created from main.
+- Changes in branches remain isolated until merged.
+- Helps in experimentation and feature development.
+
+### Commits
+- A commit saves changes to the repository.
+- Each commit has:
+    - Unique ID
+    - Commit message
+- Commit messages explain why a change was made.
+
+### Pull Requests (PR)
+- A pull request proposes changes from one branch to another.
+- Shows differences (diffs) between branches.
+- Allows review and discussion before merging.
+
+### Merging a Pull Request
+- Combines branch changes into main.
+- Conflicts must be resolved before merge.
+- After merging, branches can be deleted safely.
+
+### Benefits of Pull Requests
+- Code review
+- Quality control
+- Clear change history
+- Team collaboration