From ba13ac8a454d5d78a193b9f6efd620fa199aa650 Mon Sep 17 00:00:00 2001 From: Tanvi Limaye Date: Thu, 15 Jan 2026 11:12:18 +0530 Subject: [PATCH] refactor Add a simple change after forking --- README.md | 3 +++ chap1.txt | 3 ++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 995bfe7..5afd4bc 100644 --- a/README.md +++ b/README.md @@ -6,3 +6,6 @@ After cloning the repo, your task is to: 1. Make some changes to the code and push these changes onto the remote repository on the branch informed to you. 2. Purposely create a merge conflict in the repo and resolve it using git command line. 3. Book a one on one slot with the resource mentioned in the worksheet. + + +This is my first change after forking the repo. \ No newline at end of file diff --git a/chap1.txt b/chap1.txt index f2a53d7..e47546b 100644 --- a/chap1.txt +++ b/chap1.txt @@ -25,4 +25,5 @@ transform into world champions with tiny changes that, at first glance, would seem to make a modest difference at best? Why do small improvements accumulate into such remarkable results, and how can you replicate this approach in your own life? -This is test where I am making changes \ No newline at end of file +This is test where I am making changes +