From a4a2a5553d35758992b3690aa8a3c0be55e2e950 Mon Sep 17 00:00:00 2001 From: victorchoe Date: Fri, 6 Feb 2026 20:46:23 +0900 Subject: [PATCH 1/3] count dooku says "empiror why" --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3a87181..a2a511e 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ GitHub is a free online code hosting service that runs using git. We'll use git You should already have made an account on [GitHub](https://github.com/) and downloaded [GitHub Desktop](https://desktop.github.com/). ## 1. Fork - +두번째 저장용. *Forking* refers to the act of creating your personal copy of an existing body of code. You can then modify your *fork* as you wish. Forking is a great way to make use of templates and other resources upon which you can build. For example, you'll soon fork a template for your website, which you'll then populate and customize. Go ahead and fork this repo, using the "Fork" button at in the top-right corner. @@ -28,10 +28,10 @@ You now have a copy of this repository on GitHub. But how can you make changes? In your local clone of the repository, open this file (`README.md`). At the top of the file, underneath the title, type -> I'm \[your name\] and I edited this file! +> I'm \[Ninja\] and I edited this file! ## 4. Add and Commit - +stage를 켜야 커밋을 할 수 있다. Now go over to GitHub Desktop. Observe that the file `README.md` is now listed as changed. If there isn't already a blue checkmark beside the file, click the box to make one. Then, add a *commit message* in the box below. The commit message should be a short description of what you achieved with your code modification. For example, a good commit message here might be "Add name to README.md." Once you've entered the commit message, click the big blue Commit button. From e87974c8fc6d3d09056c44866f27fbf1c1929569 Mon Sep 17 00:00:00 2001 From: victorchoe Date: Fri, 6 Feb 2026 20:57:26 +0900 Subject: [PATCH 2/3] =?UTF-8?q?=EB=91=90=EB=B2=88=EC=A7=B8=20=EC=BB=A4?= =?UTF-8?q?=EB=B0=8B?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a2a511e..8f31700 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Practice with git and GitHub -\[Your Step 3 Edit Here\] +\[두번째 저장용이다. 풀리퀘스트가 깃 허브에 뜨나\] This is a very simple repository for practicing with git and GitHub. git is a utility for *version control*. When a body of code is tracked with git, it is easy to see how the software has evolved over time, to roll back changes when needed, and to incorporate modifications by multiple collaborators. In this activity, we're going to focus on core git workflows for single-person projects. We may do a follow-up activity later in the quarter on workflows for collaborative projects. From adf8021992c826801c42678a90326f12560e95e0 Mon Sep 17 00:00:00 2001 From: victorchoe Date: Fri, 6 Feb 2026 21:03:08 +0900 Subject: [PATCH 3/3] =?UTF-8?q?=EC=84=B8=EB=B2=88=EC=A7=B8=EB=8B=A4.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 8f31700..bf378df 100644 --- a/README.md +++ b/README.md @@ -21,6 +21,7 @@ Go ahead and fork this repo, using the "Fork" button at in the top-right corner. Check out your fork! At the moment, it's just a copy of the [original repository](https://github.com/PIC16B/git-practice). ## 2. Clone +브렌치 테스트용이다. You now have a copy of this repository on GitHub. But how can you make changes? It's possible to manually edit files on GitHub, but this is not at all convenient. Instead, you should create a *local clone* of the repository. To do this, hit the big green button and choose Open in GitHub Desktop. Choose to create the repo in a location where you'll easily remember it.