From 84f29019247e8ea9b49f23f5184175ac38b7cd13 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Mon, 5 Sep 2022 10:35:54 +0530 Subject: [PATCH 01/26] Challenge 5 Signed-off-by: Sreeja --- Challenges/challenge_5.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 Challenges/challenge_5.md diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md new file mode 100644 index 000000000..860e46c4c --- /dev/null +++ b/Challenges/challenge_5.md @@ -0,0 +1,28 @@ +## Welcome to Challenge 5 + +Welcome to the fourth challenge! +Today's goal is to update your forked repository and then create a Pull Request + +Task +1. Ensure your forked repository is in sync with the latest changes in the main repository. Also ensure that the git branch that you created in Challenge 2 is also in sync with the latest changes +2. Create a new folder inside the `contributors` folder, and name it with your github username. It should look something like this `contributors//`. Ex. + +``` +contributors/shivaylamba/ +``` + +3. Create a markdown file in the folder you created following the naming convention for the file: `.md`. Ex. + +``` +contributors/shivaylamba/shivaylamba.md +``` + +4. Copy the following template into your file, delete the placeholder text and fill the information with yours. + +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +--- +``` +5. Submit your Pull Request \ No newline at end of file From 83c3834b4dcfe4897e68311e50d190f82d58cbe4 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Mon, 5 Sep 2022 10:36:17 +0530 Subject: [PATCH 02/26] Update challenge_5.md Signed-off-by: Sreeja --- Challenges/challenge_5.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md index 860e46c4c..3d05c739f 100644 --- a/Challenges/challenge_5.md +++ b/Challenges/challenge_5.md @@ -1,6 +1,6 @@ ## Welcome to Challenge 5 -Welcome to the fourth challenge! +Welcome to the fifth challenge! Today's goal is to update your forked repository and then create a Pull Request Task @@ -25,4 +25,4 @@ name: your_name github_user_name: YOUR-GITHUB-USERNAME --- ``` -5. Submit your Pull Request \ No newline at end of file +5. Submit your Pull Request From 12f121e06f179d90937f96899a354a94968bd7da Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Mon, 5 Sep 2022 10:37:48 +0530 Subject: [PATCH 03/26] Update challenge_5.md Signed-off-by: Sreeja --- Challenges/challenge_5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md index 3d05c739f..3053335a2 100644 --- a/Challenges/challenge_5.md +++ b/Challenges/challenge_5.md @@ -25,4 +25,4 @@ name: your_name github_user_name: YOUR-GITHUB-USERNAME --- ``` -5. Submit your Pull Request +5. Submit your Pull Request on the main challenge repo. From 89bd049e3c746018d135f76974b7a5f01a61cc6f Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Tue, 6 Sep 2022 10:42:13 +0530 Subject: [PATCH 04/26] Create challenge_6.md Signed-off-by: Sreeja --- Challenges/challenge_6.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 Challenges/challenge_6.md diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md new file mode 100644 index 000000000..aea62ab79 --- /dev/null +++ b/Challenges/challenge_6.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 6 + +Welcome to the sixth challenge! +Today's goal is to update your pull request that you created in [Challenge 5](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_5.md?plain=1) + +Task +1. Create a new commit in the branch you created in Challenge 2 in your forked repository +2. The change that you have to make should be the following: +In the markdown file that was created in Challenge 5, edit the details as follows: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_isse: Link_of_the_github_issue_created_in_first_challenge +--- +``` +3. After making this change create a commit with a proper commit message and push the changes +4. Check if the commit reflects in the Pull request you created in Challenge 5 + From af597989913fa8550aa931ac677c08db0f8f12cd Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Tue, 6 Sep 2022 10:42:27 +0530 Subject: [PATCH 05/26] Update challenge_6.md Signed-off-by: Sreeja --- Challenges/challenge_6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md index aea62ab79..701d59f78 100644 --- a/Challenges/challenge_6.md +++ b/Challenges/challenge_6.md @@ -11,7 +11,7 @@ In the markdown file that was created in Challenge 5, edit the details as follow --- name: your_name github_user_name: YOUR-GITHUB-USERNAME -url_of_github_isse: Link_of_the_github_issue_created_in_first_challenge +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge --- ``` 3. After making this change create a commit with a proper commit message and push the changes From 23102e9e8faa58ab12309f5c0711fde2fc40f210 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Wed, 7 Sep 2022 11:51:57 +0530 Subject: [PATCH 06/26] Create challenge_7.md Signed-off-by: Sreeja --- Challenges/challenge_7.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 Challenges/challenge_7.md diff --git a/Challenges/challenge_7.md b/Challenges/challenge_7.md new file mode 100644 index 000000000..fe5cfb0bf --- /dev/null +++ b/Challenges/challenge_7.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 7 + +Welcome to the seventh challenge! +Today's goal is to implement the squashing of the git commits. Squashing is used to combine multiple commits into one. This is done using the interactive mode of Git Rebase command. +In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file. +So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge. + +Task: +1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges. From 868648c799a848df8375917fe062339e1d7445b2 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Thu, 1 Sep 2022 11:02:02 +0530 Subject: [PATCH 07/26] squash all commits Signed-off-by: Sreeja Saha --- CONTRIBUTING.md | 15 +++++++ Challenges/challenge_1.md | 12 +++++ Challenges/challenge_10.md | 22 ++++++++++ Challenges/challenge_11.md | 9 ++++ Challenges/challenge_12.md | 14 ++++++ Challenges/challenge_2.md | 11 +++++ Challenges/challenge_3.md | 10 +++++ Challenges/challenge_4.md | 11 +++++ Challenges/challenge_5.md | 40 +++++++++++++++++ Challenges/challenge_6.md | 19 ++++++++ Challenges/challenge_7.md | 9 ++++ Challenges/challenge_8.md | 11 +++++ Challenges/challenge_9.md | 19 ++++++++ FETCH_HEAD | 0 README.md | 58 ++++++++++++++++++++++++- contributors/shivaylamba/shivaylamba.md | 4 ++ contributors/sreejasaha19.md | 6 +++ scaler-september-open-source-challenge | 1 + 18 files changed, 270 insertions(+), 1 deletion(-) create mode 100644 CONTRIBUTING.md create mode 100644 Challenges/challenge_1.md create mode 100644 Challenges/challenge_10.md create mode 100644 Challenges/challenge_11.md create mode 100644 Challenges/challenge_12.md create mode 100644 Challenges/challenge_2.md create mode 100644 Challenges/challenge_3.md create mode 100644 Challenges/challenge_4.md create mode 100644 Challenges/challenge_5.md create mode 100644 Challenges/challenge_6.md create mode 100644 Challenges/challenge_7.md create mode 100644 Challenges/challenge_8.md create mode 100644 Challenges/challenge_9.md create mode 100644 FETCH_HEAD create mode 100644 contributors/shivaylamba/shivaylamba.md create mode 100644 contributors/sreejasaha19.md create mode 160000 scaler-september-open-source-challenge diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..5ed6b25df --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,15 @@ +## Contributing Guidelines + +Thank you for considering contributing to the repository. This guide details all the general information that one should know before contributing to the project. +Please stick as close as possible to the guidelines. That way we ensure that you have a smooth experience contributing to this project. + +### General Rules : +These are in general rules that you should be following while contributing to an Open Source project : + +- Be Nice, Be Respectful (BNBR) +- Check if the Issue you created, exists or not. +- While creating a new issue make sure you describe the issue clearly. +- Make proper commit messages and document your PR well. +- Always add Comments in your Code and explain it at points, if possible add Doctest. +- Always create a Pull Request from a Branch; Never from the Main. +- Follow proper code conventions because writing clean code is important. diff --git a/Challenges/challenge_1.md b/Challenges/challenge_1.md new file mode 100644 index 000000000..ca104e9bf --- /dev/null +++ b/Challenges/challenge_1.md @@ -0,0 +1,12 @@ +## Welcome to Challenge 1 + +Welcome to the first challenge! +We will start off with an easy task. + +Task: +Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue: + +``` +name: Add your name here +github_user_name: add your github username here +``` diff --git a/Challenges/challenge_10.md b/Challenges/challenge_10.md new file mode 100644 index 000000000..bbe1a7709 --- /dev/null +++ b/Challenges/challenge_10.md @@ -0,0 +1,22 @@ +## Welcome to Challenge 10 + +Welcome to the 10th challenge! + +Today's challenge is based on the concept of signing your commits. Signing the commits is a way of showing that only authentic commits are being made. + +A lot of open source projects have DCO which stands for [Developer Certification of Origin](https://github.com/apps/dco) including this repository itself and it tries to verify that each commit is signed or not. In case your commit is not signed it will reflect in the pull request that it doesn't pass the DCO test. + +You can read more about how to sign commits [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) + +Task: +1. Setup the ability to sign commits locally in your systems +2. Whenever committing in the future always try to use signed commits +3. Make a new signed commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +your_favroite_programming_language: Add your favorite programming language here +--- +``` diff --git a/Challenges/challenge_11.md b/Challenges/challenge_11.md new file mode 100644 index 000000000..fa1527fa9 --- /dev/null +++ b/Challenges/challenge_11.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 11 + +Welcome to the 11th challenge! + +Today's challenge is simple. + +Task: +1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main). +2. Share screenshot of this new branch in the issue created in previous challenge diff --git a/Challenges/challenge_12.md b/Challenges/challenge_12.md new file mode 100644 index 000000000..c08629ea4 --- /dev/null +++ b/Challenges/challenge_12.md @@ -0,0 +1,14 @@ +## Welcome to Challenge 12 + +Welcome to the 12th Challenge + +Today's challenge is a re-practice of the 7th Challenge (https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_7.md?plain=1) + +So focus for this challenge will be to practice the ``git rebase`` command. We still see a number of Pull requests that have a lot more commits than there should be, therefore we give you a chance to correct it again. + +Ensure to practice the ``git rebase`` command by creating your own local git repository. You can checkout this guide: https://www.freecodecamp.org/news/git-squash-explained/ + +Task: +1. Practice git rebase, and how to squash commit using git rebase in your local projects +2. Once done, try to squash the commits in your pull request in the Challenge repository +3. We also see a lot of challengers are not signing their commits. Refer to Challenge 10: https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_10.md and ensure to sign your commits. diff --git a/Challenges/challenge_2.md b/Challenges/challenge_2.md new file mode 100644 index 000000000..ebf050b64 --- /dev/null +++ b/Challenges/challenge_2.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 2 + +Welcome to the second challenge! +Today we will focus on how to fork and create a clone of a Github repository + +Task: +1. Create a fork of this repository +2. Clone the forked project locally in your system using the ``git clone`` command +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- URL of your forked repository +- A screenshot of the cloned project in your system diff --git a/Challenges/challenge_3.md b/Challenges/challenge_3.md new file mode 100644 index 000000000..835579e1c --- /dev/null +++ b/Challenges/challenge_3.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 3 + +Welcome to the third challenge! +Today we will focus on how to create a new branch in a git repository + +Task: +1. Following up on the [previous task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_2.md), create a new branch locally in your forked clone repository +2. The branch name should be as follows: ``your_github_username-details``. Example: ``shivaylamba-details`` +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the list of all the current branches inside of your forked clone repository diff --git a/Challenges/challenge_4.md b/Challenges/challenge_4.md new file mode 100644 index 000000000..42336996c --- /dev/null +++ b/Challenges/challenge_4.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 4 + +Welcome to the fourth challenge! +Today we cover how to Update Fork Repo From the Original Repo + +The main repository has been updated since the last fork that all of you created. The goal is to updated the forked repository with the changes made in the original repository. This can be done with the git command of ``git remote add upstream`` + +Task +1. Update your forked repository locally with the content of the original repository for both the main branch and the branch that you created in Challenge 3 using the ``git remote add upstream`` command +2. Once the changes in the forked repository and the original repository are synced in the git branch that you created in the 3rd Challenge, Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the latest repository contents \ No newline at end of file diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md new file mode 100644 index 000000000..43f0f8bde --- /dev/null +++ b/Challenges/challenge_5.md @@ -0,0 +1,40 @@ +## Welcome to Challenge 5 + +Welcome to the fifth challenge! +Today's goal is to update your forked repository and then create a Pull Request + +Task +1. Ensure your forked repository is in sync with the latest changes in the main repository. Also ensure that the git branch that you created in Challenge 2 is also in sync with the latest changes +2. Create a new folder inside the `contributors` folder, and name it with your github username. It should look something like this `contributors//`. Ex. + +``` +contributors/shivaylamba/ +``` + +3. Create a markdown file in the folder you created following the naming convention for the file: `.md`. Ex. + +``` +contributors/shivaylamba/shivaylamba.md +``` + +4. Copy the following template into your file, delete the placeholder text and fill the information with yours. + +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +--- +``` +<<<<<<< HEAD +<<<<<<< HEAD +<<<<<<< HEAD +5. Submit your Pull Request on the main challenge repo. +======= +5. Submit your Pull Request +>>>>>>> 2496816 (Update challenge_5.md) +======= +5. Submit your Pull Request on the main challenge repo. +>>>>>>> 866d6780cf0a9e4033a50a7c8fa23570e8e50bf6 +======= +5. Submit your Pull Request on the main challenge repo. +>>>>>>> 693d4c386f40060aa7ee5a6f6fd2c4b4d4fb2992 diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md new file mode 100644 index 000000000..701d59f78 --- /dev/null +++ b/Challenges/challenge_6.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 6 + +Welcome to the sixth challenge! +Today's goal is to update your pull request that you created in [Challenge 5](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_5.md?plain=1) + +Task +1. Create a new commit in the branch you created in Challenge 2 in your forked repository +2. The change that you have to make should be the following: +In the markdown file that was created in Challenge 5, edit the details as follows: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +--- +``` +3. After making this change create a commit with a proper commit message and push the changes +4. Check if the commit reflects in the Pull request you created in Challenge 5 + diff --git a/Challenges/challenge_7.md b/Challenges/challenge_7.md new file mode 100644 index 000000000..fe5cfb0bf --- /dev/null +++ b/Challenges/challenge_7.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 7 + +Welcome to the seventh challenge! +Today's goal is to implement the squashing of the git commits. Squashing is used to combine multiple commits into one. This is done using the interactive mode of Git Rebase command. +In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file. +So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge. + +Task: +1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges. diff --git a/Challenges/challenge_8.md b/Challenges/challenge_8.md new file mode 100644 index 000000000..a143bd663 --- /dev/null +++ b/Challenges/challenge_8.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 8 + +Welcome to the 8th challenge! + +Today's challenge is simple. But along side the task, please give the [following article](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) a read, as this will be used in Challenge 9. + + +Task: +1. Inside the branch you created during the prior challenges in your forked repository, make a new file by the name of ``your-github-username-2.md`` and add any details you may want to add to this markwdown file and push the change + +2. Ensure the change appears in the Pull request created in previous challenges diff --git a/Challenges/challenge_9.md b/Challenges/challenge_9.md new file mode 100644 index 000000000..895473b94 --- /dev/null +++ b/Challenges/challenge_9.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 9 + +Welcome to the ninth challenge! + +Today's task is a continuation of yesterday's task [Task 8](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_8.md?plain=1). + +Yesterday the task was to create an additional commit in your branch. And today's focus will be to remove that commit that has been pushed from the pull request created in previous challenges. The main purpose of this is because there can be times when you might push an unncessary or wrong commit and you way want to remove it from your pull request. + +This can be done by using the following command: ``git reset`` + +Here is an article you can refer to for understanding how git reset works: https://www.atlassian.com/git/tutorials/undoing-changes/git-reset#:~:text=a%20shared%20repository.-,Summary,Index%2C%20and%20the%20Working%20Directory. + +So the task is to identity the commit id of the commit you want to remove, use the git reset command, and remove the commit from the pull request by force pushing into it. + + +Task: +1. Identify the commit id that needs to be removed (you should have created this in the 8th Challenge) +2. Use git reset and force push, to remove the commit from your pull request. +3. Share a screenshot of this, in the issue you created in previous challenges. diff --git a/FETCH_HEAD b/FETCH_HEAD new file mode 100644 index 000000000..e69de29bb diff --git a/README.md b/README.md index f61ab9b42..6c03e71e7 100644 --- a/README.md +++ b/README.md @@ -1 +1,57 @@ -# scaler-september-open-source-challenge \ No newline at end of file +# Scaler September Open Source Challenge + + +

+ +

+ + +## What is the Scaler September Open Source Challenge? +Link for [Notion page](https://scalerdiscord.notion.site/scalerdiscord/Open-Source-September-Scaler-Discord-Community-f9306c7dc15a464ba1b6ea7ee30cdf0d). + +Every day throughout September, for those who have enrolled, we will share one task.  +Participants will need to use their knowledge of Git and Github for each task, and the difficulty level of the tasks will rise daily. + +The primary objective? To help the community become better at contributing to open source and building projects. + +## Learning Outcomes +1. Learn how to contribute to open source projects. Learn the basics of creating issues, pull requests, Git and Github +2. Celebrate with new rewards every time you reach a milestone! + +## How to participate? + +### Step 1 + +Accept the challenge by filling out this form: [https://bit.ly/opensourcesepbyscaler](https://bit.ly/opensourcesepbyscaler) + +### Step 2 + +If you haven't already, create an account on Github, and brush up on your skills in Git and Github. + +### Step 3 + +Head to the official [Scaler Open Source challenge repository](https://github.com/scaleracademy/scaler-september-open-source-challenge/). Star it. + +Keep track of the README, as a new task will be added every day. + +Please go through the task for that day and solve it. + +### Step 4 + +Don't forget to share your progress within the community if you want those rewards! + +## Prizes +Consistency is what we're after. As a result, we have several levels or awards based on how consistently you complete the assignments. +You won't be qualified for the remaining tasks of the challenge if you are unable to complete and submit a task on any given day. + +Here is the reward [tier list](https://scalerdiscord.notion.site/3eabe9a1900c4b8685ae55acb5c33cbe?v=001e8d4c287f4d96bae935c5d45de521). + +## Contact Us +For all communications and queries, you can join our [Discord Server](https://discord.com/invite/scaler). + +## Resources +1. Launch Video for the September Challenge: [Guide to Github and the Open Source Challenge](https://youtu.be/70nx_YxE56Q) +2. Git Tutorial: [Full Git Tutorial](https://www.youtube.com/watch?v=ZtfZGVQWjew) +3. Find good first issues to contribute to: [Good First issues](https://goodfirstissue.dev/) +4. Getting started with Github: [All you need to know about Github](https://www.youtube.com/watch?v=8WYXWs96xxc) +5. How to contribute to Open Source: [Open Source contribution guide](https://www.youtube.com/watch?v=ABty2r3nDyU) diff --git a/contributors/shivaylamba/shivaylamba.md b/contributors/shivaylamba/shivaylamba.md new file mode 100644 index 000000000..6e3107508 --- /dev/null +++ b/contributors/shivaylamba/shivaylamba.md @@ -0,0 +1,4 @@ +--- +name: Shivay Lamba +github_user: shivaylamba +--- \ No newline at end of file diff --git a/contributors/sreejasaha19.md b/contributors/sreejasaha19.md new file mode 100644 index 000000000..d8d594a55 --- /dev/null +++ b/contributors/sreejasaha19.md @@ -0,0 +1,6 @@ +--- +name: Sreeja Saha +github_user_name: sreejasaha19 +url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/126#issue-1358568239 +your_favroite_programming_language: Python +--- diff --git a/scaler-september-open-source-challenge b/scaler-september-open-source-challenge new file mode 160000 index 000000000..c23ba1b6f --- /dev/null +++ b/scaler-september-open-source-challenge @@ -0,0 +1 @@ +Subproject commit c23ba1b6faee0f8385537ab54fdc496edbd02f40 From 92bc68a23277bad498e464773375a4199cdaf684 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Tue, 13 Sep 2022 23:03:51 +0530 Subject: [PATCH 08/26] Created temp.md --- contributors/sreejasaha19/temp.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 contributors/sreejasaha19/temp.md diff --git a/contributors/sreejasaha19/temp.md b/contributors/sreejasaha19/temp.md new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/contributors/sreejasaha19/temp.md @@ -0,0 +1 @@ + From 2a10286b2a875f2d7410ca3bf309ec0385b73ea5 Mon Sep 17 00:00:00 2001 From: Sreeja Saha Date: Tue, 13 Sep 2022 23:44:10 +0530 Subject: [PATCH 09/26] commit message --- Challenges/challenge_13.md | 10 ++++++++++ Challenges/challenge_5.md | 4 ++++ 2 files changed, 14 insertions(+) create mode 100644 Challenges/challenge_13.md diff --git a/Challenges/challenge_13.md b/Challenges/challenge_13.md new file mode 100644 index 000000000..9744d811a --- /dev/null +++ b/Challenges/challenge_13.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 13 + +Welcome to the 13th Challenge + +Today's challenge involves how to use ``git stash`` command effectively. You can refer on how to stash your commits [here](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning) + +Task: +1. Inside the branch you created in the previous challenge ``your-username-details`` create a new file inside the ``contributors//`` directory. +2. Use the git stash command to move these changes to the stash area +3. Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first challenge diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md index 43f0f8bde..dfa1800dd 100644 --- a/Challenges/challenge_5.md +++ b/Challenges/challenge_5.md @@ -28,6 +28,7 @@ github_user_name: YOUR-GITHUB-USERNAME <<<<<<< HEAD <<<<<<< HEAD <<<<<<< HEAD +<<<<<<< HEAD 5. Submit your Pull Request on the main challenge repo. ======= 5. Submit your Pull Request @@ -38,3 +39,6 @@ github_user_name: YOUR-GITHUB-USERNAME ======= 5. Submit your Pull Request on the main challenge repo. >>>>>>> 693d4c386f40060aa7ee5a6f6fd2c4b4d4fb2992 +======= +5. Submit your Pull Request on the main challenge repo. +>>>>>>> c6bd8de53b8b3c97ebbc4f8b6971c2b282d65dc4 From 3b1dfb9c10e03890e89d12346a8981bbfdf2ab2e Mon Sep 17 00:00:00 2001 From: Sreeja Saha Date: Tue, 13 Sep 2022 23:56:22 +0530 Subject: [PATCH 10/26] msg --- Challenges/challenge_5.md | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md index dfa1800dd..3053335a2 100644 --- a/Challenges/challenge_5.md +++ b/Challenges/challenge_5.md @@ -25,20 +25,4 @@ name: your_name github_user_name: YOUR-GITHUB-USERNAME --- ``` -<<<<<<< HEAD -<<<<<<< HEAD -<<<<<<< HEAD -<<<<<<< HEAD 5. Submit your Pull Request on the main challenge repo. -======= -5. Submit your Pull Request ->>>>>>> 2496816 (Update challenge_5.md) -======= -5. Submit your Pull Request on the main challenge repo. ->>>>>>> 866d6780cf0a9e4033a50a7c8fa23570e8e50bf6 -======= -5. Submit your Pull Request on the main challenge repo. ->>>>>>> 693d4c386f40060aa7ee5a6f6fd2c4b4d4fb2992 -======= -5. Submit your Pull Request on the main challenge repo. ->>>>>>> c6bd8de53b8b3c97ebbc4f8b6971c2b282d65dc4 From c92cf4eb5b0213683f7ae2c88c5e8e765e111fb9 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Thu, 1 Sep 2022 11:02:02 +0530 Subject: [PATCH 11/26] squash all commits Signed-off-by: Sreeja Saha --- CONTRIBUTING.md | 15 +++++++ Challenges/challenge_1.md | 12 +++++ Challenges/challenge_10.md | 22 ++++++++++ Challenges/challenge_11.md | 9 ++++ Challenges/challenge_12.md | 14 ++++++ Challenges/challenge_13.md | 10 +++++ Challenges/challenge_2.md | 11 +++++ Challenges/challenge_3.md | 10 +++++ Challenges/challenge_4.md | 11 +++++ Challenges/challenge_5.md | 44 +++++++++++++++++++ Challenges/challenge_6.md | 19 ++++++++ Challenges/challenge_7.md | 9 ++++ Challenges/challenge_8.md | 11 +++++ Challenges/challenge_9.md | 19 ++++++++ FETCH_HEAD | 0 README.md | 58 ++++++++++++++++++++++++- contributors/shivaylamba/shivaylamba.md | 4 ++ contributors/sreejasaha19.md | 6 +++ scaler-september-open-source-challenge | 1 + 19 files changed, 284 insertions(+), 1 deletion(-) create mode 100644 CONTRIBUTING.md create mode 100644 Challenges/challenge_1.md create mode 100644 Challenges/challenge_10.md create mode 100644 Challenges/challenge_11.md create mode 100644 Challenges/challenge_12.md create mode 100644 Challenges/challenge_13.md create mode 100644 Challenges/challenge_2.md create mode 100644 Challenges/challenge_3.md create mode 100644 Challenges/challenge_4.md create mode 100644 Challenges/challenge_5.md create mode 100644 Challenges/challenge_6.md create mode 100644 Challenges/challenge_7.md create mode 100644 Challenges/challenge_8.md create mode 100644 Challenges/challenge_9.md create mode 100644 FETCH_HEAD create mode 100644 contributors/shivaylamba/shivaylamba.md create mode 100644 contributors/sreejasaha19.md create mode 160000 scaler-september-open-source-challenge diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..5ed6b25df --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,15 @@ +## Contributing Guidelines + +Thank you for considering contributing to the repository. This guide details all the general information that one should know before contributing to the project. +Please stick as close as possible to the guidelines. That way we ensure that you have a smooth experience contributing to this project. + +### General Rules : +These are in general rules that you should be following while contributing to an Open Source project : + +- Be Nice, Be Respectful (BNBR) +- Check if the Issue you created, exists or not. +- While creating a new issue make sure you describe the issue clearly. +- Make proper commit messages and document your PR well. +- Always add Comments in your Code and explain it at points, if possible add Doctest. +- Always create a Pull Request from a Branch; Never from the Main. +- Follow proper code conventions because writing clean code is important. diff --git a/Challenges/challenge_1.md b/Challenges/challenge_1.md new file mode 100644 index 000000000..ca104e9bf --- /dev/null +++ b/Challenges/challenge_1.md @@ -0,0 +1,12 @@ +## Welcome to Challenge 1 + +Welcome to the first challenge! +We will start off with an easy task. + +Task: +Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue: + +``` +name: Add your name here +github_user_name: add your github username here +``` diff --git a/Challenges/challenge_10.md b/Challenges/challenge_10.md new file mode 100644 index 000000000..bbe1a7709 --- /dev/null +++ b/Challenges/challenge_10.md @@ -0,0 +1,22 @@ +## Welcome to Challenge 10 + +Welcome to the 10th challenge! + +Today's challenge is based on the concept of signing your commits. Signing the commits is a way of showing that only authentic commits are being made. + +A lot of open source projects have DCO which stands for [Developer Certification of Origin](https://github.com/apps/dco) including this repository itself and it tries to verify that each commit is signed or not. In case your commit is not signed it will reflect in the pull request that it doesn't pass the DCO test. + +You can read more about how to sign commits [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) + +Task: +1. Setup the ability to sign commits locally in your systems +2. Whenever committing in the future always try to use signed commits +3. Make a new signed commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +your_favroite_programming_language: Add your favorite programming language here +--- +``` diff --git a/Challenges/challenge_11.md b/Challenges/challenge_11.md new file mode 100644 index 000000000..fa1527fa9 --- /dev/null +++ b/Challenges/challenge_11.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 11 + +Welcome to the 11th challenge! + +Today's challenge is simple. + +Task: +1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main). +2. Share screenshot of this new branch in the issue created in previous challenge diff --git a/Challenges/challenge_12.md b/Challenges/challenge_12.md new file mode 100644 index 000000000..c08629ea4 --- /dev/null +++ b/Challenges/challenge_12.md @@ -0,0 +1,14 @@ +## Welcome to Challenge 12 + +Welcome to the 12th Challenge + +Today's challenge is a re-practice of the 7th Challenge (https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_7.md?plain=1) + +So focus for this challenge will be to practice the ``git rebase`` command. We still see a number of Pull requests that have a lot more commits than there should be, therefore we give you a chance to correct it again. + +Ensure to practice the ``git rebase`` command by creating your own local git repository. You can checkout this guide: https://www.freecodecamp.org/news/git-squash-explained/ + +Task: +1. Practice git rebase, and how to squash commit using git rebase in your local projects +2. Once done, try to squash the commits in your pull request in the Challenge repository +3. We also see a lot of challengers are not signing their commits. Refer to Challenge 10: https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_10.md and ensure to sign your commits. diff --git a/Challenges/challenge_13.md b/Challenges/challenge_13.md new file mode 100644 index 000000000..9744d811a --- /dev/null +++ b/Challenges/challenge_13.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 13 + +Welcome to the 13th Challenge + +Today's challenge involves how to use ``git stash`` command effectively. You can refer on how to stash your commits [here](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning) + +Task: +1. Inside the branch you created in the previous challenge ``your-username-details`` create a new file inside the ``contributors//`` directory. +2. Use the git stash command to move these changes to the stash area +3. Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first challenge diff --git a/Challenges/challenge_2.md b/Challenges/challenge_2.md new file mode 100644 index 000000000..ebf050b64 --- /dev/null +++ b/Challenges/challenge_2.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 2 + +Welcome to the second challenge! +Today we will focus on how to fork and create a clone of a Github repository + +Task: +1. Create a fork of this repository +2. Clone the forked project locally in your system using the ``git clone`` command +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- URL of your forked repository +- A screenshot of the cloned project in your system diff --git a/Challenges/challenge_3.md b/Challenges/challenge_3.md new file mode 100644 index 000000000..835579e1c --- /dev/null +++ b/Challenges/challenge_3.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 3 + +Welcome to the third challenge! +Today we will focus on how to create a new branch in a git repository + +Task: +1. Following up on the [previous task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_2.md), create a new branch locally in your forked clone repository +2. The branch name should be as follows: ``your_github_username-details``. Example: ``shivaylamba-details`` +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the list of all the current branches inside of your forked clone repository diff --git a/Challenges/challenge_4.md b/Challenges/challenge_4.md new file mode 100644 index 000000000..42336996c --- /dev/null +++ b/Challenges/challenge_4.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 4 + +Welcome to the fourth challenge! +Today we cover how to Update Fork Repo From the Original Repo + +The main repository has been updated since the last fork that all of you created. The goal is to updated the forked repository with the changes made in the original repository. This can be done with the git command of ``git remote add upstream`` + +Task +1. Update your forked repository locally with the content of the original repository for both the main branch and the branch that you created in Challenge 3 using the ``git remote add upstream`` command +2. Once the changes in the forked repository and the original repository are synced in the git branch that you created in the 3rd Challenge, Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the latest repository contents \ No newline at end of file diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md new file mode 100644 index 000000000..dfa1800dd --- /dev/null +++ b/Challenges/challenge_5.md @@ -0,0 +1,44 @@ +## Welcome to Challenge 5 + +Welcome to the fifth challenge! +Today's goal is to update your forked repository and then create a Pull Request + +Task +1. Ensure your forked repository is in sync with the latest changes in the main repository. Also ensure that the git branch that you created in Challenge 2 is also in sync with the latest changes +2. Create a new folder inside the `contributors` folder, and name it with your github username. It should look something like this `contributors//`. Ex. + +``` +contributors/shivaylamba/ +``` + +3. Create a markdown file in the folder you created following the naming convention for the file: `.md`. Ex. + +``` +contributors/shivaylamba/shivaylamba.md +``` + +4. Copy the following template into your file, delete the placeholder text and fill the information with yours. + +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +--- +``` +<<<<<<< HEAD +<<<<<<< HEAD +<<<<<<< HEAD +<<<<<<< HEAD +5. Submit your Pull Request on the main challenge repo. +======= +5. Submit your Pull Request +>>>>>>> 2496816 (Update challenge_5.md) +======= +5. Submit your Pull Request on the main challenge repo. +>>>>>>> 866d6780cf0a9e4033a50a7c8fa23570e8e50bf6 +======= +5. Submit your Pull Request on the main challenge repo. +>>>>>>> 693d4c386f40060aa7ee5a6f6fd2c4b4d4fb2992 +======= +5. Submit your Pull Request on the main challenge repo. +>>>>>>> c6bd8de53b8b3c97ebbc4f8b6971c2b282d65dc4 diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md new file mode 100644 index 000000000..701d59f78 --- /dev/null +++ b/Challenges/challenge_6.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 6 + +Welcome to the sixth challenge! +Today's goal is to update your pull request that you created in [Challenge 5](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_5.md?plain=1) + +Task +1. Create a new commit in the branch you created in Challenge 2 in your forked repository +2. The change that you have to make should be the following: +In the markdown file that was created in Challenge 5, edit the details as follows: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +--- +``` +3. After making this change create a commit with a proper commit message and push the changes +4. Check if the commit reflects in the Pull request you created in Challenge 5 + diff --git a/Challenges/challenge_7.md b/Challenges/challenge_7.md new file mode 100644 index 000000000..fe5cfb0bf --- /dev/null +++ b/Challenges/challenge_7.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 7 + +Welcome to the seventh challenge! +Today's goal is to implement the squashing of the git commits. Squashing is used to combine multiple commits into one. This is done using the interactive mode of Git Rebase command. +In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file. +So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge. + +Task: +1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges. diff --git a/Challenges/challenge_8.md b/Challenges/challenge_8.md new file mode 100644 index 000000000..a143bd663 --- /dev/null +++ b/Challenges/challenge_8.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 8 + +Welcome to the 8th challenge! + +Today's challenge is simple. But along side the task, please give the [following article](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) a read, as this will be used in Challenge 9. + + +Task: +1. Inside the branch you created during the prior challenges in your forked repository, make a new file by the name of ``your-github-username-2.md`` and add any details you may want to add to this markwdown file and push the change + +2. Ensure the change appears in the Pull request created in previous challenges diff --git a/Challenges/challenge_9.md b/Challenges/challenge_9.md new file mode 100644 index 000000000..895473b94 --- /dev/null +++ b/Challenges/challenge_9.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 9 + +Welcome to the ninth challenge! + +Today's task is a continuation of yesterday's task [Task 8](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_8.md?plain=1). + +Yesterday the task was to create an additional commit in your branch. And today's focus will be to remove that commit that has been pushed from the pull request created in previous challenges. The main purpose of this is because there can be times when you might push an unncessary or wrong commit and you way want to remove it from your pull request. + +This can be done by using the following command: ``git reset`` + +Here is an article you can refer to for understanding how git reset works: https://www.atlassian.com/git/tutorials/undoing-changes/git-reset#:~:text=a%20shared%20repository.-,Summary,Index%2C%20and%20the%20Working%20Directory. + +So the task is to identity the commit id of the commit you want to remove, use the git reset command, and remove the commit from the pull request by force pushing into it. + + +Task: +1. Identify the commit id that needs to be removed (you should have created this in the 8th Challenge) +2. Use git reset and force push, to remove the commit from your pull request. +3. Share a screenshot of this, in the issue you created in previous challenges. diff --git a/FETCH_HEAD b/FETCH_HEAD new file mode 100644 index 000000000..e69de29bb diff --git a/README.md b/README.md index f61ab9b42..6c03e71e7 100644 --- a/README.md +++ b/README.md @@ -1 +1,57 @@ -# scaler-september-open-source-challenge \ No newline at end of file +# Scaler September Open Source Challenge + + +

+ +

+ + +## What is the Scaler September Open Source Challenge? +Link for [Notion page](https://scalerdiscord.notion.site/scalerdiscord/Open-Source-September-Scaler-Discord-Community-f9306c7dc15a464ba1b6ea7ee30cdf0d). + +Every day throughout September, for those who have enrolled, we will share one task.  +Participants will need to use their knowledge of Git and Github for each task, and the difficulty level of the tasks will rise daily. + +The primary objective? To help the community become better at contributing to open source and building projects. + +## Learning Outcomes +1. Learn how to contribute to open source projects. Learn the basics of creating issues, pull requests, Git and Github +2. Celebrate with new rewards every time you reach a milestone! + +## How to participate? + +### Step 1 + +Accept the challenge by filling out this form: [https://bit.ly/opensourcesepbyscaler](https://bit.ly/opensourcesepbyscaler) + +### Step 2 + +If you haven't already, create an account on Github, and brush up on your skills in Git and Github. + +### Step 3 + +Head to the official [Scaler Open Source challenge repository](https://github.com/scaleracademy/scaler-september-open-source-challenge/). Star it. + +Keep track of the README, as a new task will be added every day. + +Please go through the task for that day and solve it. + +### Step 4 + +Don't forget to share your progress within the community if you want those rewards! + +## Prizes +Consistency is what we're after. As a result, we have several levels or awards based on how consistently you complete the assignments. +You won't be qualified for the remaining tasks of the challenge if you are unable to complete and submit a task on any given day. + +Here is the reward [tier list](https://scalerdiscord.notion.site/3eabe9a1900c4b8685ae55acb5c33cbe?v=001e8d4c287f4d96bae935c5d45de521). + +## Contact Us +For all communications and queries, you can join our [Discord Server](https://discord.com/invite/scaler). + +## Resources +1. Launch Video for the September Challenge: [Guide to Github and the Open Source Challenge](https://youtu.be/70nx_YxE56Q) +2. Git Tutorial: [Full Git Tutorial](https://www.youtube.com/watch?v=ZtfZGVQWjew) +3. Find good first issues to contribute to: [Good First issues](https://goodfirstissue.dev/) +4. Getting started with Github: [All you need to know about Github](https://www.youtube.com/watch?v=8WYXWs96xxc) +5. How to contribute to Open Source: [Open Source contribution guide](https://www.youtube.com/watch?v=ABty2r3nDyU) diff --git a/contributors/shivaylamba/shivaylamba.md b/contributors/shivaylamba/shivaylamba.md new file mode 100644 index 000000000..6e3107508 --- /dev/null +++ b/contributors/shivaylamba/shivaylamba.md @@ -0,0 +1,4 @@ +--- +name: Shivay Lamba +github_user: shivaylamba +--- \ No newline at end of file diff --git a/contributors/sreejasaha19.md b/contributors/sreejasaha19.md new file mode 100644 index 000000000..d8d594a55 --- /dev/null +++ b/contributors/sreejasaha19.md @@ -0,0 +1,6 @@ +--- +name: Sreeja Saha +github_user_name: sreejasaha19 +url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/126#issue-1358568239 +your_favroite_programming_language: Python +--- diff --git a/scaler-september-open-source-challenge b/scaler-september-open-source-challenge new file mode 160000 index 000000000..c23ba1b6f --- /dev/null +++ b/scaler-september-open-source-challenge @@ -0,0 +1 @@ +Subproject commit c23ba1b6faee0f8385537ab54fdc496edbd02f40 From 2a3f6ac8f0b4f3bd96635b18d1a9f6dcf2f94f85 Mon Sep 17 00:00:00 2001 From: Sreeja Saha Date: Tue, 13 Sep 2022 23:56:22 +0530 Subject: [PATCH 12/26] Created temp.md Signed-off-by: Sreeja Saha --- Challenges/challenge_5.md | 16 ---------------- contributors/sreejasaha19/temp.md | 1 + 2 files changed, 1 insertion(+), 16 deletions(-) create mode 100644 contributors/sreejasaha19/temp.md diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md index dfa1800dd..3053335a2 100644 --- a/Challenges/challenge_5.md +++ b/Challenges/challenge_5.md @@ -25,20 +25,4 @@ name: your_name github_user_name: YOUR-GITHUB-USERNAME --- ``` -<<<<<<< HEAD -<<<<<<< HEAD -<<<<<<< HEAD -<<<<<<< HEAD 5. Submit your Pull Request on the main challenge repo. -======= -5. Submit your Pull Request ->>>>>>> 2496816 (Update challenge_5.md) -======= -5. Submit your Pull Request on the main challenge repo. ->>>>>>> 866d6780cf0a9e4033a50a7c8fa23570e8e50bf6 -======= -5. Submit your Pull Request on the main challenge repo. ->>>>>>> 693d4c386f40060aa7ee5a6f6fd2c4b4d4fb2992 -======= -5. Submit your Pull Request on the main challenge repo. ->>>>>>> c6bd8de53b8b3c97ebbc4f8b6971c2b282d65dc4 diff --git a/contributors/sreejasaha19/temp.md b/contributors/sreejasaha19/temp.md new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/contributors/sreejasaha19/temp.md @@ -0,0 +1 @@ + From 930c2dcd2515afdc638aaaf1ff47c8ecff813783 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Thu, 1 Sep 2022 11:02:02 +0530 Subject: [PATCH 13/26] squash all commits Signed-off-by: Sreeja Saha Created temp.md Signed-off-by: Sreeja Saha --- CONTRIBUTING.md | 15 +++++++ Challenges/challenge_1.md | 12 +++++ Challenges/challenge_10.md | 22 ++++++++++ Challenges/challenge_11.md | 9 ++++ Challenges/challenge_12.md | 14 ++++++ Challenges/challenge_13.md | 10 +++++ Challenges/challenge_2.md | 11 +++++ Challenges/challenge_3.md | 10 +++++ Challenges/challenge_4.md | 11 +++++ Challenges/challenge_5.md | 28 ++++++++++++ Challenges/challenge_6.md | 19 ++++++++ Challenges/challenge_7.md | 9 ++++ Challenges/challenge_8.md | 11 +++++ Challenges/challenge_9.md | 19 ++++++++ FETCH_HEAD | 0 README.md | 58 ++++++++++++++++++++++++- contributors/shivaylamba/shivaylamba.md | 4 ++ contributors/sreejasaha19.md | 6 +++ contributors/sreejasaha19/temp.md | 1 + scaler-september-open-source-challenge | 1 + 20 files changed, 269 insertions(+), 1 deletion(-) create mode 100644 CONTRIBUTING.md create mode 100644 Challenges/challenge_1.md create mode 100644 Challenges/challenge_10.md create mode 100644 Challenges/challenge_11.md create mode 100644 Challenges/challenge_12.md create mode 100644 Challenges/challenge_13.md create mode 100644 Challenges/challenge_2.md create mode 100644 Challenges/challenge_3.md create mode 100644 Challenges/challenge_4.md create mode 100644 Challenges/challenge_5.md create mode 100644 Challenges/challenge_6.md create mode 100644 Challenges/challenge_7.md create mode 100644 Challenges/challenge_8.md create mode 100644 Challenges/challenge_9.md create mode 100644 FETCH_HEAD create mode 100644 contributors/shivaylamba/shivaylamba.md create mode 100644 contributors/sreejasaha19.md create mode 100644 contributors/sreejasaha19/temp.md create mode 160000 scaler-september-open-source-challenge diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..5ed6b25df --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,15 @@ +## Contributing Guidelines + +Thank you for considering contributing to the repository. This guide details all the general information that one should know before contributing to the project. +Please stick as close as possible to the guidelines. That way we ensure that you have a smooth experience contributing to this project. + +### General Rules : +These are in general rules that you should be following while contributing to an Open Source project : + +- Be Nice, Be Respectful (BNBR) +- Check if the Issue you created, exists or not. +- While creating a new issue make sure you describe the issue clearly. +- Make proper commit messages and document your PR well. +- Always add Comments in your Code and explain it at points, if possible add Doctest. +- Always create a Pull Request from a Branch; Never from the Main. +- Follow proper code conventions because writing clean code is important. diff --git a/Challenges/challenge_1.md b/Challenges/challenge_1.md new file mode 100644 index 000000000..ca104e9bf --- /dev/null +++ b/Challenges/challenge_1.md @@ -0,0 +1,12 @@ +## Welcome to Challenge 1 + +Welcome to the first challenge! +We will start off with an easy task. + +Task: +Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue: + +``` +name: Add your name here +github_user_name: add your github username here +``` diff --git a/Challenges/challenge_10.md b/Challenges/challenge_10.md new file mode 100644 index 000000000..bbe1a7709 --- /dev/null +++ b/Challenges/challenge_10.md @@ -0,0 +1,22 @@ +## Welcome to Challenge 10 + +Welcome to the 10th challenge! + +Today's challenge is based on the concept of signing your commits. Signing the commits is a way of showing that only authentic commits are being made. + +A lot of open source projects have DCO which stands for [Developer Certification of Origin](https://github.com/apps/dco) including this repository itself and it tries to verify that each commit is signed or not. In case your commit is not signed it will reflect in the pull request that it doesn't pass the DCO test. + +You can read more about how to sign commits [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) + +Task: +1. Setup the ability to sign commits locally in your systems +2. Whenever committing in the future always try to use signed commits +3. Make a new signed commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +your_favroite_programming_language: Add your favorite programming language here +--- +``` diff --git a/Challenges/challenge_11.md b/Challenges/challenge_11.md new file mode 100644 index 000000000..fa1527fa9 --- /dev/null +++ b/Challenges/challenge_11.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 11 + +Welcome to the 11th challenge! + +Today's challenge is simple. + +Task: +1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main). +2. Share screenshot of this new branch in the issue created in previous challenge diff --git a/Challenges/challenge_12.md b/Challenges/challenge_12.md new file mode 100644 index 000000000..c08629ea4 --- /dev/null +++ b/Challenges/challenge_12.md @@ -0,0 +1,14 @@ +## Welcome to Challenge 12 + +Welcome to the 12th Challenge + +Today's challenge is a re-practice of the 7th Challenge (https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_7.md?plain=1) + +So focus for this challenge will be to practice the ``git rebase`` command. We still see a number of Pull requests that have a lot more commits than there should be, therefore we give you a chance to correct it again. + +Ensure to practice the ``git rebase`` command by creating your own local git repository. You can checkout this guide: https://www.freecodecamp.org/news/git-squash-explained/ + +Task: +1. Practice git rebase, and how to squash commit using git rebase in your local projects +2. Once done, try to squash the commits in your pull request in the Challenge repository +3. We also see a lot of challengers are not signing their commits. Refer to Challenge 10: https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_10.md and ensure to sign your commits. diff --git a/Challenges/challenge_13.md b/Challenges/challenge_13.md new file mode 100644 index 000000000..9744d811a --- /dev/null +++ b/Challenges/challenge_13.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 13 + +Welcome to the 13th Challenge + +Today's challenge involves how to use ``git stash`` command effectively. You can refer on how to stash your commits [here](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning) + +Task: +1. Inside the branch you created in the previous challenge ``your-username-details`` create a new file inside the ``contributors//`` directory. +2. Use the git stash command to move these changes to the stash area +3. Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first challenge diff --git a/Challenges/challenge_2.md b/Challenges/challenge_2.md new file mode 100644 index 000000000..ebf050b64 --- /dev/null +++ b/Challenges/challenge_2.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 2 + +Welcome to the second challenge! +Today we will focus on how to fork and create a clone of a Github repository + +Task: +1. Create a fork of this repository +2. Clone the forked project locally in your system using the ``git clone`` command +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- URL of your forked repository +- A screenshot of the cloned project in your system diff --git a/Challenges/challenge_3.md b/Challenges/challenge_3.md new file mode 100644 index 000000000..835579e1c --- /dev/null +++ b/Challenges/challenge_3.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 3 + +Welcome to the third challenge! +Today we will focus on how to create a new branch in a git repository + +Task: +1. Following up on the [previous task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_2.md), create a new branch locally in your forked clone repository +2. The branch name should be as follows: ``your_github_username-details``. Example: ``shivaylamba-details`` +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the list of all the current branches inside of your forked clone repository diff --git a/Challenges/challenge_4.md b/Challenges/challenge_4.md new file mode 100644 index 000000000..42336996c --- /dev/null +++ b/Challenges/challenge_4.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 4 + +Welcome to the fourth challenge! +Today we cover how to Update Fork Repo From the Original Repo + +The main repository has been updated since the last fork that all of you created. The goal is to updated the forked repository with the changes made in the original repository. This can be done with the git command of ``git remote add upstream`` + +Task +1. Update your forked repository locally with the content of the original repository for both the main branch and the branch that you created in Challenge 3 using the ``git remote add upstream`` command +2. Once the changes in the forked repository and the original repository are synced in the git branch that you created in the 3rd Challenge, Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the latest repository contents \ No newline at end of file diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md new file mode 100644 index 000000000..3053335a2 --- /dev/null +++ b/Challenges/challenge_5.md @@ -0,0 +1,28 @@ +## Welcome to Challenge 5 + +Welcome to the fifth challenge! +Today's goal is to update your forked repository and then create a Pull Request + +Task +1. Ensure your forked repository is in sync with the latest changes in the main repository. Also ensure that the git branch that you created in Challenge 2 is also in sync with the latest changes +2. Create a new folder inside the `contributors` folder, and name it with your github username. It should look something like this `contributors//`. Ex. + +``` +contributors/shivaylamba/ +``` + +3. Create a markdown file in the folder you created following the naming convention for the file: `.md`. Ex. + +``` +contributors/shivaylamba/shivaylamba.md +``` + +4. Copy the following template into your file, delete the placeholder text and fill the information with yours. + +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +--- +``` +5. Submit your Pull Request on the main challenge repo. diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md new file mode 100644 index 000000000..701d59f78 --- /dev/null +++ b/Challenges/challenge_6.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 6 + +Welcome to the sixth challenge! +Today's goal is to update your pull request that you created in [Challenge 5](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_5.md?plain=1) + +Task +1. Create a new commit in the branch you created in Challenge 2 in your forked repository +2. The change that you have to make should be the following: +In the markdown file that was created in Challenge 5, edit the details as follows: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +--- +``` +3. After making this change create a commit with a proper commit message and push the changes +4. Check if the commit reflects in the Pull request you created in Challenge 5 + diff --git a/Challenges/challenge_7.md b/Challenges/challenge_7.md new file mode 100644 index 000000000..fe5cfb0bf --- /dev/null +++ b/Challenges/challenge_7.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 7 + +Welcome to the seventh challenge! +Today's goal is to implement the squashing of the git commits. Squashing is used to combine multiple commits into one. This is done using the interactive mode of Git Rebase command. +In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file. +So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge. + +Task: +1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges. diff --git a/Challenges/challenge_8.md b/Challenges/challenge_8.md new file mode 100644 index 000000000..a143bd663 --- /dev/null +++ b/Challenges/challenge_8.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 8 + +Welcome to the 8th challenge! + +Today's challenge is simple. But along side the task, please give the [following article](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) a read, as this will be used in Challenge 9. + + +Task: +1. Inside the branch you created during the prior challenges in your forked repository, make a new file by the name of ``your-github-username-2.md`` and add any details you may want to add to this markwdown file and push the change + +2. Ensure the change appears in the Pull request created in previous challenges diff --git a/Challenges/challenge_9.md b/Challenges/challenge_9.md new file mode 100644 index 000000000..895473b94 --- /dev/null +++ b/Challenges/challenge_9.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 9 + +Welcome to the ninth challenge! + +Today's task is a continuation of yesterday's task [Task 8](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_8.md?plain=1). + +Yesterday the task was to create an additional commit in your branch. And today's focus will be to remove that commit that has been pushed from the pull request created in previous challenges. The main purpose of this is because there can be times when you might push an unncessary or wrong commit and you way want to remove it from your pull request. + +This can be done by using the following command: ``git reset`` + +Here is an article you can refer to for understanding how git reset works: https://www.atlassian.com/git/tutorials/undoing-changes/git-reset#:~:text=a%20shared%20repository.-,Summary,Index%2C%20and%20the%20Working%20Directory. + +So the task is to identity the commit id of the commit you want to remove, use the git reset command, and remove the commit from the pull request by force pushing into it. + + +Task: +1. Identify the commit id that needs to be removed (you should have created this in the 8th Challenge) +2. Use git reset and force push, to remove the commit from your pull request. +3. Share a screenshot of this, in the issue you created in previous challenges. diff --git a/FETCH_HEAD b/FETCH_HEAD new file mode 100644 index 000000000..e69de29bb diff --git a/README.md b/README.md index f61ab9b42..6c03e71e7 100644 --- a/README.md +++ b/README.md @@ -1 +1,57 @@ -# scaler-september-open-source-challenge \ No newline at end of file +# Scaler September Open Source Challenge + + +

+ +

+ + +## What is the Scaler September Open Source Challenge? +Link for [Notion page](https://scalerdiscord.notion.site/scalerdiscord/Open-Source-September-Scaler-Discord-Community-f9306c7dc15a464ba1b6ea7ee30cdf0d). + +Every day throughout September, for those who have enrolled, we will share one task.  +Participants will need to use their knowledge of Git and Github for each task, and the difficulty level of the tasks will rise daily. + +The primary objective? To help the community become better at contributing to open source and building projects. + +## Learning Outcomes +1. Learn how to contribute to open source projects. Learn the basics of creating issues, pull requests, Git and Github +2. Celebrate with new rewards every time you reach a milestone! + +## How to participate? + +### Step 1 + +Accept the challenge by filling out this form: [https://bit.ly/opensourcesepbyscaler](https://bit.ly/opensourcesepbyscaler) + +### Step 2 + +If you haven't already, create an account on Github, and brush up on your skills in Git and Github. + +### Step 3 + +Head to the official [Scaler Open Source challenge repository](https://github.com/scaleracademy/scaler-september-open-source-challenge/). Star it. + +Keep track of the README, as a new task will be added every day. + +Please go through the task for that day and solve it. + +### Step 4 + +Don't forget to share your progress within the community if you want those rewards! + +## Prizes +Consistency is what we're after. As a result, we have several levels or awards based on how consistently you complete the assignments. +You won't be qualified for the remaining tasks of the challenge if you are unable to complete and submit a task on any given day. + +Here is the reward [tier list](https://scalerdiscord.notion.site/3eabe9a1900c4b8685ae55acb5c33cbe?v=001e8d4c287f4d96bae935c5d45de521). + +## Contact Us +For all communications and queries, you can join our [Discord Server](https://discord.com/invite/scaler). + +## Resources +1. Launch Video for the September Challenge: [Guide to Github and the Open Source Challenge](https://youtu.be/70nx_YxE56Q) +2. Git Tutorial: [Full Git Tutorial](https://www.youtube.com/watch?v=ZtfZGVQWjew) +3. Find good first issues to contribute to: [Good First issues](https://goodfirstissue.dev/) +4. Getting started with Github: [All you need to know about Github](https://www.youtube.com/watch?v=8WYXWs96xxc) +5. How to contribute to Open Source: [Open Source contribution guide](https://www.youtube.com/watch?v=ABty2r3nDyU) diff --git a/contributors/shivaylamba/shivaylamba.md b/contributors/shivaylamba/shivaylamba.md new file mode 100644 index 000000000..6e3107508 --- /dev/null +++ b/contributors/shivaylamba/shivaylamba.md @@ -0,0 +1,4 @@ +--- +name: Shivay Lamba +github_user: shivaylamba +--- \ No newline at end of file diff --git a/contributors/sreejasaha19.md b/contributors/sreejasaha19.md new file mode 100644 index 000000000..d8d594a55 --- /dev/null +++ b/contributors/sreejasaha19.md @@ -0,0 +1,6 @@ +--- +name: Sreeja Saha +github_user_name: sreejasaha19 +url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/126#issue-1358568239 +your_favroite_programming_language: Python +--- diff --git a/contributors/sreejasaha19/temp.md b/contributors/sreejasaha19/temp.md new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/contributors/sreejasaha19/temp.md @@ -0,0 +1 @@ + diff --git a/scaler-september-open-source-challenge b/scaler-september-open-source-challenge new file mode 160000 index 000000000..c23ba1b6f --- /dev/null +++ b/scaler-september-open-source-challenge @@ -0,0 +1 @@ +Subproject commit c23ba1b6faee0f8385537ab54fdc496edbd02f40 From fb726904f16e8c8cdca75f88ab6ef88c8d82fab9 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Wed, 14 Sep 2022 05:27:32 +0530 Subject: [PATCH 14/26] Delete temp.md --- contributors/sreejasaha19/temp.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 contributors/sreejasaha19/temp.md diff --git a/contributors/sreejasaha19/temp.md b/contributors/sreejasaha19/temp.md deleted file mode 100644 index 8b1378917..000000000 --- a/contributors/sreejasaha19/temp.md +++ /dev/null @@ -1 +0,0 @@ - From 4c01c1492def4f794e9cf21371665341691a32a4 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Wed, 14 Sep 2022 05:45:01 +0530 Subject: [PATCH 15/26] Created temp.md --- contributors/sreejasaha19/temp.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 contributors/sreejasaha19/temp.md diff --git a/contributors/sreejasaha19/temp.md b/contributors/sreejasaha19/temp.md new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/contributors/sreejasaha19/temp.md @@ -0,0 +1 @@ + From 734d90f1553ab499a05fb9768251b05aedb0a6c6 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Thu, 1 Sep 2022 11:02:02 +0530 Subject: [PATCH 16/26] squash all commits Signed-off-by: Sreeja Saha Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- CONTRIBUTING.md | 15 ++++++ Challenges/challenge_1.md | 12 +++++ Challenges/challenge_10.md | 22 +++++++++ Challenges/challenge_11.md | 9 ++++ Challenges/challenge_12.md | 14 ++++++ Challenges/challenge_13.md | 10 ++++ Challenges/challenge_2.md | 11 +++++ Challenges/challenge_3.md | 10 ++++ Challenges/challenge_4.md | 11 +++++ Challenges/challenge_5.md | 28 +++++++++++ Challenges/challenge_6.md | 19 ++++++++ Challenges/challenge_7.md | 9 ++++ Challenges/challenge_8.md | 11 +++++ Challenges/challenge_9.md | 19 ++++++++ FETCH_HEAD | 0 README.md | 58 ++++++++++++++++++++++- contributors/shivaylamba/shivaylamba.md | 4 ++ contributors/sreejasaha19/sreejasaha19.md | 6 +++ scaler-september-open-source-challenge | 1 + 19 files changed, 268 insertions(+), 1 deletion(-) create mode 100644 CONTRIBUTING.md create mode 100644 Challenges/challenge_1.md create mode 100644 Challenges/challenge_10.md create mode 100644 Challenges/challenge_11.md create mode 100644 Challenges/challenge_12.md create mode 100644 Challenges/challenge_13.md create mode 100644 Challenges/challenge_2.md create mode 100644 Challenges/challenge_3.md create mode 100644 Challenges/challenge_4.md create mode 100644 Challenges/challenge_5.md create mode 100644 Challenges/challenge_6.md create mode 100644 Challenges/challenge_7.md create mode 100644 Challenges/challenge_8.md create mode 100644 Challenges/challenge_9.md create mode 100644 FETCH_HEAD create mode 100644 contributors/shivaylamba/shivaylamba.md create mode 100644 contributors/sreejasaha19/sreejasaha19.md create mode 160000 scaler-september-open-source-challenge diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..5ed6b25df --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,15 @@ +## Contributing Guidelines + +Thank you for considering contributing to the repository. This guide details all the general information that one should know before contributing to the project. +Please stick as close as possible to the guidelines. That way we ensure that you have a smooth experience contributing to this project. + +### General Rules : +These are in general rules that you should be following while contributing to an Open Source project : + +- Be Nice, Be Respectful (BNBR) +- Check if the Issue you created, exists or not. +- While creating a new issue make sure you describe the issue clearly. +- Make proper commit messages and document your PR well. +- Always add Comments in your Code and explain it at points, if possible add Doctest. +- Always create a Pull Request from a Branch; Never from the Main. +- Follow proper code conventions because writing clean code is important. diff --git a/Challenges/challenge_1.md b/Challenges/challenge_1.md new file mode 100644 index 000000000..ca104e9bf --- /dev/null +++ b/Challenges/challenge_1.md @@ -0,0 +1,12 @@ +## Welcome to Challenge 1 + +Welcome to the first challenge! +We will start off with an easy task. + +Task: +Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue: + +``` +name: Add your name here +github_user_name: add your github username here +``` diff --git a/Challenges/challenge_10.md b/Challenges/challenge_10.md new file mode 100644 index 000000000..bbe1a7709 --- /dev/null +++ b/Challenges/challenge_10.md @@ -0,0 +1,22 @@ +## Welcome to Challenge 10 + +Welcome to the 10th challenge! + +Today's challenge is based on the concept of signing your commits. Signing the commits is a way of showing that only authentic commits are being made. + +A lot of open source projects have DCO which stands for [Developer Certification of Origin](https://github.com/apps/dco) including this repository itself and it tries to verify that each commit is signed or not. In case your commit is not signed it will reflect in the pull request that it doesn't pass the DCO test. + +You can read more about how to sign commits [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) + +Task: +1. Setup the ability to sign commits locally in your systems +2. Whenever committing in the future always try to use signed commits +3. Make a new signed commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +your_favroite_programming_language: Add your favorite programming language here +--- +``` diff --git a/Challenges/challenge_11.md b/Challenges/challenge_11.md new file mode 100644 index 000000000..fa1527fa9 --- /dev/null +++ b/Challenges/challenge_11.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 11 + +Welcome to the 11th challenge! + +Today's challenge is simple. + +Task: +1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main). +2. Share screenshot of this new branch in the issue created in previous challenge diff --git a/Challenges/challenge_12.md b/Challenges/challenge_12.md new file mode 100644 index 000000000..c08629ea4 --- /dev/null +++ b/Challenges/challenge_12.md @@ -0,0 +1,14 @@ +## Welcome to Challenge 12 + +Welcome to the 12th Challenge + +Today's challenge is a re-practice of the 7th Challenge (https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_7.md?plain=1) + +So focus for this challenge will be to practice the ``git rebase`` command. We still see a number of Pull requests that have a lot more commits than there should be, therefore we give you a chance to correct it again. + +Ensure to practice the ``git rebase`` command by creating your own local git repository. You can checkout this guide: https://www.freecodecamp.org/news/git-squash-explained/ + +Task: +1. Practice git rebase, and how to squash commit using git rebase in your local projects +2. Once done, try to squash the commits in your pull request in the Challenge repository +3. We also see a lot of challengers are not signing their commits. Refer to Challenge 10: https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_10.md and ensure to sign your commits. diff --git a/Challenges/challenge_13.md b/Challenges/challenge_13.md new file mode 100644 index 000000000..9744d811a --- /dev/null +++ b/Challenges/challenge_13.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 13 + +Welcome to the 13th Challenge + +Today's challenge involves how to use ``git stash`` command effectively. You can refer on how to stash your commits [here](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning) + +Task: +1. Inside the branch you created in the previous challenge ``your-username-details`` create a new file inside the ``contributors//`` directory. +2. Use the git stash command to move these changes to the stash area +3. Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first challenge diff --git a/Challenges/challenge_2.md b/Challenges/challenge_2.md new file mode 100644 index 000000000..ebf050b64 --- /dev/null +++ b/Challenges/challenge_2.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 2 + +Welcome to the second challenge! +Today we will focus on how to fork and create a clone of a Github repository + +Task: +1. Create a fork of this repository +2. Clone the forked project locally in your system using the ``git clone`` command +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- URL of your forked repository +- A screenshot of the cloned project in your system diff --git a/Challenges/challenge_3.md b/Challenges/challenge_3.md new file mode 100644 index 000000000..835579e1c --- /dev/null +++ b/Challenges/challenge_3.md @@ -0,0 +1,10 @@ +## Welcome to Challenge 3 + +Welcome to the third challenge! +Today we will focus on how to create a new branch in a git repository + +Task: +1. Following up on the [previous task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_2.md), create a new branch locally in your forked clone repository +2. The branch name should be as follows: ``your_github_username-details``. Example: ``shivaylamba-details`` +3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the list of all the current branches inside of your forked clone repository diff --git a/Challenges/challenge_4.md b/Challenges/challenge_4.md new file mode 100644 index 000000000..42336996c --- /dev/null +++ b/Challenges/challenge_4.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 4 + +Welcome to the fourth challenge! +Today we cover how to Update Fork Repo From the Original Repo + +The main repository has been updated since the last fork that all of you created. The goal is to updated the forked repository with the changes made in the original repository. This can be done with the git command of ``git remote add upstream`` + +Task +1. Update your forked repository locally with the content of the original repository for both the main branch and the branch that you created in Challenge 3 using the ``git remote add upstream`` command +2. Once the changes in the forked repository and the original repository are synced in the git branch that you created in the 3rd Challenge, Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: +- Screenshot showing the latest repository contents \ No newline at end of file diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md new file mode 100644 index 000000000..3053335a2 --- /dev/null +++ b/Challenges/challenge_5.md @@ -0,0 +1,28 @@ +## Welcome to Challenge 5 + +Welcome to the fifth challenge! +Today's goal is to update your forked repository and then create a Pull Request + +Task +1. Ensure your forked repository is in sync with the latest changes in the main repository. Also ensure that the git branch that you created in Challenge 2 is also in sync with the latest changes +2. Create a new folder inside the `contributors` folder, and name it with your github username. It should look something like this `contributors//`. Ex. + +``` +contributors/shivaylamba/ +``` + +3. Create a markdown file in the folder you created following the naming convention for the file: `.md`. Ex. + +``` +contributors/shivaylamba/shivaylamba.md +``` + +4. Copy the following template into your file, delete the placeholder text and fill the information with yours. + +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +--- +``` +5. Submit your Pull Request on the main challenge repo. diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md new file mode 100644 index 000000000..701d59f78 --- /dev/null +++ b/Challenges/challenge_6.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 6 + +Welcome to the sixth challenge! +Today's goal is to update your pull request that you created in [Challenge 5](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_5.md?plain=1) + +Task +1. Create a new commit in the branch you created in Challenge 2 in your forked repository +2. The change that you have to make should be the following: +In the markdown file that was created in Challenge 5, edit the details as follows: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +--- +``` +3. After making this change create a commit with a proper commit message and push the changes +4. Check if the commit reflects in the Pull request you created in Challenge 5 + diff --git a/Challenges/challenge_7.md b/Challenges/challenge_7.md new file mode 100644 index 000000000..fe5cfb0bf --- /dev/null +++ b/Challenges/challenge_7.md @@ -0,0 +1,9 @@ +## Welcome to Challenge 7 + +Welcome to the seventh challenge! +Today's goal is to implement the squashing of the git commits. Squashing is used to combine multiple commits into one. This is done using the interactive mode of Git Rebase command. +In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file. +So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge. + +Task: +1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges. diff --git a/Challenges/challenge_8.md b/Challenges/challenge_8.md new file mode 100644 index 000000000..a143bd663 --- /dev/null +++ b/Challenges/challenge_8.md @@ -0,0 +1,11 @@ +## Welcome to Challenge 8 + +Welcome to the 8th challenge! + +Today's challenge is simple. But along side the task, please give the [following article](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) a read, as this will be used in Challenge 9. + + +Task: +1. Inside the branch you created during the prior challenges in your forked repository, make a new file by the name of ``your-github-username-2.md`` and add any details you may want to add to this markwdown file and push the change + +2. Ensure the change appears in the Pull request created in previous challenges diff --git a/Challenges/challenge_9.md b/Challenges/challenge_9.md new file mode 100644 index 000000000..895473b94 --- /dev/null +++ b/Challenges/challenge_9.md @@ -0,0 +1,19 @@ +## Welcome to Challenge 9 + +Welcome to the ninth challenge! + +Today's task is a continuation of yesterday's task [Task 8](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_8.md?plain=1). + +Yesterday the task was to create an additional commit in your branch. And today's focus will be to remove that commit that has been pushed from the pull request created in previous challenges. The main purpose of this is because there can be times when you might push an unncessary or wrong commit and you way want to remove it from your pull request. + +This can be done by using the following command: ``git reset`` + +Here is an article you can refer to for understanding how git reset works: https://www.atlassian.com/git/tutorials/undoing-changes/git-reset#:~:text=a%20shared%20repository.-,Summary,Index%2C%20and%20the%20Working%20Directory. + +So the task is to identity the commit id of the commit you want to remove, use the git reset command, and remove the commit from the pull request by force pushing into it. + + +Task: +1. Identify the commit id that needs to be removed (you should have created this in the 8th Challenge) +2. Use git reset and force push, to remove the commit from your pull request. +3. Share a screenshot of this, in the issue you created in previous challenges. diff --git a/FETCH_HEAD b/FETCH_HEAD new file mode 100644 index 000000000..e69de29bb diff --git a/README.md b/README.md index f61ab9b42..6c03e71e7 100644 --- a/README.md +++ b/README.md @@ -1 +1,57 @@ -# scaler-september-open-source-challenge \ No newline at end of file +# Scaler September Open Source Challenge + + +

+ +

+ + +## What is the Scaler September Open Source Challenge? +Link for [Notion page](https://scalerdiscord.notion.site/scalerdiscord/Open-Source-September-Scaler-Discord-Community-f9306c7dc15a464ba1b6ea7ee30cdf0d). + +Every day throughout September, for those who have enrolled, we will share one task.  +Participants will need to use their knowledge of Git and Github for each task, and the difficulty level of the tasks will rise daily. + +The primary objective? To help the community become better at contributing to open source and building projects. + +## Learning Outcomes +1. Learn how to contribute to open source projects. Learn the basics of creating issues, pull requests, Git and Github +2. Celebrate with new rewards every time you reach a milestone! + +## How to participate? + +### Step 1 + +Accept the challenge by filling out this form: [https://bit.ly/opensourcesepbyscaler](https://bit.ly/opensourcesepbyscaler) + +### Step 2 + +If you haven't already, create an account on Github, and brush up on your skills in Git and Github. + +### Step 3 + +Head to the official [Scaler Open Source challenge repository](https://github.com/scaleracademy/scaler-september-open-source-challenge/). Star it. + +Keep track of the README, as a new task will be added every day. + +Please go through the task for that day and solve it. + +### Step 4 + +Don't forget to share your progress within the community if you want those rewards! + +## Prizes +Consistency is what we're after. As a result, we have several levels or awards based on how consistently you complete the assignments. +You won't be qualified for the remaining tasks of the challenge if you are unable to complete and submit a task on any given day. + +Here is the reward [tier list](https://scalerdiscord.notion.site/3eabe9a1900c4b8685ae55acb5c33cbe?v=001e8d4c287f4d96bae935c5d45de521). + +## Contact Us +For all communications and queries, you can join our [Discord Server](https://discord.com/invite/scaler). + +## Resources +1. Launch Video for the September Challenge: [Guide to Github and the Open Source Challenge](https://youtu.be/70nx_YxE56Q) +2. Git Tutorial: [Full Git Tutorial](https://www.youtube.com/watch?v=ZtfZGVQWjew) +3. Find good first issues to contribute to: [Good First issues](https://goodfirstissue.dev/) +4. Getting started with Github: [All you need to know about Github](https://www.youtube.com/watch?v=8WYXWs96xxc) +5. How to contribute to Open Source: [Open Source contribution guide](https://www.youtube.com/watch?v=ABty2r3nDyU) diff --git a/contributors/shivaylamba/shivaylamba.md b/contributors/shivaylamba/shivaylamba.md new file mode 100644 index 000000000..6e3107508 --- /dev/null +++ b/contributors/shivaylamba/shivaylamba.md @@ -0,0 +1,4 @@ +--- +name: Shivay Lamba +github_user: shivaylamba +--- \ No newline at end of file diff --git a/contributors/sreejasaha19/sreejasaha19.md b/contributors/sreejasaha19/sreejasaha19.md new file mode 100644 index 000000000..d8d594a55 --- /dev/null +++ b/contributors/sreejasaha19/sreejasaha19.md @@ -0,0 +1,6 @@ +--- +name: Sreeja Saha +github_user_name: sreejasaha19 +url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/126#issue-1358568239 +your_favroite_programming_language: Python +--- diff --git a/scaler-september-open-source-challenge b/scaler-september-open-source-challenge new file mode 160000 index 000000000..c23ba1b6f --- /dev/null +++ b/scaler-september-open-source-challenge @@ -0,0 +1 @@ +Subproject commit c23ba1b6faee0f8385537ab54fdc496edbd02f40 From a546c58ffd2125e47a7115425729850ffad74282 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Sun, 18 Sep 2022 20:22:32 +0530 Subject: [PATCH 17/26] Created gist-solutions.md Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- contributors/sreejasaha19/gist-solutions.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 contributors/sreejasaha19/gist-solutions.md diff --git a/contributors/sreejasaha19/gist-solutions.md b/contributors/sreejasaha19/gist-solutions.md new file mode 100644 index 000000000..8ede6a912 --- /dev/null +++ b/contributors/sreejasaha19/gist-solutions.md @@ -0,0 +1,5 @@ +# Link of software development related topic gist +https://gist.github.com/sreejasaha19/4c9c957498177bc8f48ceea79c068378 + +# Link of code snippet in Python gist +https://gist.github.com/sreejasaha19/6942bf46f17cffc4cd4f9ed5152f2d69 \ No newline at end of file From 822062f835ea4e04e8a5142fcc545d7639a403f1 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Mon, 19 Sep 2022 23:07:40 +0530 Subject: [PATCH 18/26] Linted Markdown files Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- contributors/sreejasaha19/gist-solutions.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/contributors/sreejasaha19/gist-solutions.md b/contributors/sreejasaha19/gist-solutions.md index 8ede6a912..12769c9a3 100644 --- a/contributors/sreejasaha19/gist-solutions.md +++ b/contributors/sreejasaha19/gist-solutions.md @@ -1,5 +1,4 @@ -# Link of software development related topic gist -https://gist.github.com/sreejasaha19/4c9c957498177bc8f48ceea79c068378 - -# Link of code snippet in Python gist -https://gist.github.com/sreejasaha19/6942bf46f17cffc4cd4f9ed5152f2d69 \ No newline at end of file +--- +Link of software development related topic gist:https://gist.github.com/sreejasaha19/4c9c957498177bc8f48ceea79c068378 +Link of code snippet in Python gist:https://gist.github.com/sreejasaha19/6942bf46f17cffc4cd4f9ed5152f2d69 +--- \ No newline at end of file From 9aa8f7b4915bc6baadfb9b9bd03a44e5fedf17c0 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Mon, 19 Sep 2022 23:10:13 +0530 Subject: [PATCH 19/26] Created demo_code.py Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- contributors/sreejasaha19/demo_code.py | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 contributors/sreejasaha19/demo_code.py diff --git a/contributors/sreejasaha19/demo_code.py b/contributors/sreejasaha19/demo_code.py new file mode 100644 index 000000000..571f332a5 --- /dev/null +++ b/contributors/sreejasaha19/demo_code.py @@ -0,0 +1,10 @@ +""" Basic python program to print hello world""" + + +def greet(): + + """Function to print Hello world""" + print("Hello world") + + +greet() From c5602440821a9a61227cbddc073e4b62309a4aa5 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Tue, 20 Sep 2022 02:04:22 +0530 Subject: [PATCH 20/26] Created gist-solutions.md Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- contributors/sreejasaha19/gist-solutions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributors/sreejasaha19/gist-solutions.md b/contributors/sreejasaha19/gist-solutions.md index 12769c9a3..e63505f6d 100644 --- a/contributors/sreejasaha19/gist-solutions.md +++ b/contributors/sreejasaha19/gist-solutions.md @@ -1,4 +1,4 @@ --- -Link of software development related topic gist:https://gist.github.com/sreejasaha19/4c9c957498177bc8f48ceea79c068378 -Link of code snippet in Python gist:https://gist.github.com/sreejasaha19/6942bf46f17cffc4cd4f9ed5152f2d69 +Link of software development related topic gist: https://gist.github.com/sreejasaha19/4c9c957498177bc8f48ceea79c068378 +Link of code snippet in Python gist: https://gist.github.com/sreejasaha19/6942bf46f17cffc4cd4f9ed5152f2d69 --- \ No newline at end of file From 8060925803b2dd2dcf91b3752ab2512dcc3fe68c Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Tue, 20 Sep 2022 02:36:34 +0530 Subject: [PATCH 21/26] Added my name in challengers list Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- challengers-list.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 challengers-list.md diff --git a/challengers-list.md b/challengers-list.md new file mode 100644 index 000000000..ba41c1a09 --- /dev/null +++ b/challengers-list.md @@ -0,0 +1,5 @@ +# List of challengers +1. [Mrinal](https://github.com/mrinal1224) +2. [Shivay](https://github.com/shivaylamba) +3. [Sreeja Saha](https://github.com/sreejasaha19) +3. [Raghav](https://github.com/raghavdhingra) From 56e2a979dcff80546d7a3369fbac89cc98734894 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Tue, 20 Sep 2022 02:42:13 +0530 Subject: [PATCH 22/26] Resolve Conflict Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- challengers-list.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/challengers-list.md b/challengers-list.md index ba41c1a09..e985c39cc 100644 --- a/challengers-list.md +++ b/challengers-list.md @@ -1,5 +1,5 @@ # List of challengers 1. [Mrinal](https://github.com/mrinal1224) 2. [Shivay](https://github.com/shivaylamba) -3. [Sreeja Saha](https://github.com/sreejasaha19) 3. [Raghav](https://github.com/raghavdhingra) +4. [Sreeja Saha](https://github.com/sreejasaha19) From 20295c19e51c7020be40151074b1d42fb5ba9464 Mon Sep 17 00:00:00 2001 From: Shivay Lamba Date: Thu, 22 Sep 2022 10:55:42 +0530 Subject: [PATCH 23/26] 22 Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- Challenges/challenge_22.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 Challenges/challenge_22.md diff --git a/Challenges/challenge_22.md b/Challenges/challenge_22.md new file mode 100644 index 000000000..48c7ac770 --- /dev/null +++ b/Challenges/challenge_22.md @@ -0,0 +1,32 @@ +## Welcome to Challenge 22 + +Welcome to the 22nd Challenge + +Today we will learn how to work with GitHub pages! + +#### Brief Overview + +GitHub pages allows GitHub users to host static websites on GitHub's server for free. To learn more visit the official [GitHub Pages site](https://pages.github.com/) + +## Tasks + +- Create a new repository on GitHub +- Create a basic static website about yourself +- Add your html site to your respository. +- Host your site on GitHub pages + +## How to Submit + + +- Make a new commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file that exists inside the ``contributors\your-user-name`` directory in the following format: +``` +--- +name: your_name +github_user_name: YOUR-GITHUB-USERNAME +url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge +your_favroite_programming_language: Add your favorite programming language here +your_hosted_github_pages_link: Add your hosted github page link here +your_hosted_github_pages_repository_link: Add your repository link here +--- +``` +- Add screenshots of your site to the pull request \ No newline at end of file From d20ce5e050cd6bdce0ab9189e0820c93fb83365f Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Thu, 22 Sep 2022 19:53:19 +0530 Subject: [PATCH 24/26] Updated sreejasaha19.md Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- contributors/sreejasaha19/sreejasaha19.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/contributors/sreejasaha19/sreejasaha19.md b/contributors/sreejasaha19/sreejasaha19.md index d8d594a55..11c123684 100644 --- a/contributors/sreejasaha19/sreejasaha19.md +++ b/contributors/sreejasaha19/sreejasaha19.md @@ -3,4 +3,6 @@ name: Sreeja Saha github_user_name: sreejasaha19 url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/126#issue-1358568239 your_favroite_programming_language: Python +your_hosted_github_pages_link: https://sreejasaha19.github.io/ +your_hosted_github_pages_repository_link: https://github.com/sreejasaha19/sreejasaha19.github.io --- From 064745a9b6588f25ef1355d87cfd58e06894b4af Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Thu, 22 Sep 2022 21:43:20 +0530 Subject: [PATCH 25/26] Updated challengers-list.md Signed-off-by: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> --- vim | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 vim diff --git a/vim b/vim new file mode 100644 index 000000000..e69de29bb From 079c60ffc11e2cc436fd5ece8b0a5e79559c9da1 Mon Sep 17 00:00:00 2001 From: sreejasaha19 <105979237+sreejasaha19@users.noreply.github.com> Date: Thu, 22 Sep 2022 22:12:28 +0530 Subject: [PATCH 26/26] Delete vim --- vim | 0 1 file changed, 0 insertions(+), 0 deletions(-) delete mode 100644 vim diff --git a/vim b/vim deleted file mode 100644 index e69de29bb..000000000