Squashed in one

Merged all commits

Signed-off-by: Rishav986 <[email protected]>

Signed-off-by: Rishav986 <[email protected]>

Signed-off-by: Rishav986 <[email protected]>

Squashed Challenge7

Signed-off-by: Rishav986 <[email protected]>

Create challenge_8.md

Signed-off-by: Rishav986 <[email protected]>

Signed-off-by: Rishav986 <[email protected]>

Create Rishav986-2.md

Signed-off-by: Rishav986 <[email protected]>

Revert "Create Rishav986-2.md"

Signed-off-by: Rishav986 <[email protected]>

Update Rishav986.md

Signed-off-by: Rishav986 <[email protected]>

Create challenge_11.md

Signed-off-by: Rishav986 <[email protected]>

Create challenge_12.md

Signed-off-by: Rishav986 <[email protected]>

Update challenge_12.md

Signed-off-by: Rishav986 <[email protected]>

Create challenge_13.md

Signed-off-by: Rishav986 <[email protected]>

Update challenge_13.md

Signed-off-by: Rishav986 <[email protected]>

Create challenge_14.md

Signed-off-by: Rishav986 <[email protected]>

Challenge15

Signed-off-by: Rishav986 <[email protected]>

small update

Signed-off-by: Rishav986 <[email protected]>

Challenge 15 - Added my name in challengers list.

Signed-off-by: Rishav986 <[email protected]>

Author: shivaylamba

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
+---
+```

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

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. 

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/<YOUR-GITHUB_USERNAME>/`` 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

Challenges/challenge_14.md

@@ -0,0 +1,11 @@
+## Welcome to Challenge 14
+
+Welcome to the 14th Challenge 
+
+Today is the first part of the two challenges related to resolving merge conflicts. You can take a look at [this article](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) to learn more about merge conflicts. 
+
+As part of the challenge, try to create a scenario of a merge conflict locally in your system for a project that you can create. 
+
+Task: 
+1. Follow the article shared above and try to reproduce a case of merge conflict in your system for a project and try to resolve it 
+2. Share appropriate screenshot in the issue created in the first challenge. 

Challenges/challenge_15.md

@@ -0,0 +1,15 @@
+## Welcome to Challenge 15
+
+Welcome to the 15th Challenge 
+
+In this 2 part challenge, we will try to emulate and fix merge conflicts via git. 
+
+Today is the first part of this challenge: 
+
+Task: 
+1. Update your Forked Repo From the Original Repo. Also ensure that your branch ``your-user-name-details`` is also synced with the latest changes from the original repository
+
+2. In your branch ``your-user-name-details`` open the add your name to the list of challengers inside the ``challengers-list.md`` file by following the format in the file. 
+
+3. Push your change to reflect in the Pull Request created in previous challenges
+

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

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/<YOUR-GITHUB_USERNAME>/`. Ex.
+
+```
+contributors/shivaylamba/
+```
+
+3. Create a markdown file in the folder you created following the naming convention for the file: `<YOUR-GITHUB-USERNAME>.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.

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
+

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. 

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

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. 

challengers-list.md

@@ -0,0 +1,4 @@
+# List of challengers
+1. [Mrinal](https://github.com/mrinal1224)
+2. [Shivay](https://github.com/shivaylamba)
+3. [Rishav](https://github.com/Rishav986)

contributors/Rishav986/Rishav986.md

@@ -0,0 +1,6 @@
+---
+name: Rishav Siwach
+github_user_name: Rishav986
+url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/215
+your_favroite_programming_language: Python
+---

contributors/shivaylamba/shivaylamba.md

@@ -0,0 +1,4 @@
+---
+name: Shivay Lamba
+github_user: shivaylamba
+---