From 595a0f7c25db217eebebcdba430205240b5f11fd Mon Sep 17 00:00:00 2001 From: Nyadej Date: Wed, 29 May 2024 15:56:49 +0100 Subject: [PATCH 1/3] ticked off comppleted tasks and created markdown file --- README.md | 8 ++++---- markdown.md | 7 +++++++ 2 files changed, 11 insertions(+), 4 deletions(-) create mode 100644 markdown.md diff --git a/README.md b/README.md index 5256046..1843ea0 100644 --- a/README.md +++ b/README.md @@ -94,10 +94,10 @@ You can check out the GitHub Explore website [at github.com/explore](https://git ## Tasks * Fork (copy) this repository under your personal GitHub account by clicking the green `<> Code` button - * Invite your mentor or someone in the tech team as a [collaborator](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository) — ask them for their GitHub username if you don't know it - * Create a new branch in your fork and and create a new Markdown file. Share what you've learned and what you're still confused about. Experiment with different styles! - * Open a pull request and add your mentor as a [reviewer](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) (**note:** they must first accept your collaboration request to be available as a reviewer). -* Create your profile README. Let the world know a little bit more about you! What are you interested in learning? What are you working on? What's your favorite hobby? Learn more about creating your profile README in the document, ["Managing Your Profile README"](https://docs.github.com/en/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme). + * Invite your mentor or someone in the tech team as a [collaborator](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository) — ask them for their GitHub username if you don't know it ✅ + * Create a new branch in your fork and and create a new Markdown file. Share what you've learned and what you're still confused about. Experiment with different styles! ✅ + * Open a pull request and add your mentor as a [reviewer](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) (**note:** they must first accept your collaboration request to be available as a reviewer). ✅ +* Create your profile README. Let the world know a little bit more about you! What are you interested in learning? What are you working on? What's your favorite hobby? Learn more about creating your profile README in the document, ["Managing Your Profile README"](https://docs.github.com/en/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme). ✅ * Go to your user dashboard and create a new repository. Experiment with the features within that repository to familiarize yourself with them. * [Let us know what you liked or didn’t like about the content of this course](https://support.github.com/contact/education). What would you like to see more of? What would be interesting or helpful to your learning journey? diff --git a/markdown.md b/markdown.md new file mode 100644 index 0000000..768945f --- /dev/null +++ b/markdown.md @@ -0,0 +1,7 @@ +# Create a new branch in your fork and and create a new Markdown file. Share what you've learned + +I learnt how to fork a repository from git and create a new branch + file within this. + +# what you're still confused about. + +nothing. \ No newline at end of file From 2b0d41d1947800b1a65c0862e3753cdb226a9de1 Mon Sep 17 00:00:00 2001 From: Nyadej Date: Thu, 30 May 2024 15:12:20 +0100 Subject: [PATCH 2/3] new branch added --- markdown.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/markdown.md b/markdown.md index 768945f..2c90cf5 100644 --- a/markdown.md +++ b/markdown.md @@ -4,4 +4,6 @@ I learnt how to fork a repository from git and create a new branch + file within # what you're still confused about. -nothing. \ No newline at end of file +nothing. + +new changes added. \ No newline at end of file From 8d0aee9bd8eb772f15ecb668dba4ce7877eb5420 Mon Sep 17 00:00:00 2001 From: Nyadej Date: Thu, 30 May 2024 15:35:55 +0100 Subject: [PATCH 3/3] changes --- github-fundamentals | 1 + markdown.md | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) create mode 160000 github-fundamentals diff --git a/github-fundamentals b/github-fundamentals new file mode 160000 index 0000000..595a0f7 --- /dev/null +++ b/github-fundamentals @@ -0,0 +1 @@ +Subproject commit 595a0f7c25db217eebebcdba430205240b5f11fd diff --git a/markdown.md b/markdown.md index 2c90cf5..c413ce9 100644 --- a/markdown.md +++ b/markdown.md @@ -6,4 +6,5 @@ I learnt how to fork a repository from git and create a new branch + file within nothing. -new changes added. \ No newline at end of file +new changes added. +additional changes. \ No newline at end of file