file added

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_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. 

contributors/shivaylamba/shivaylamba.md

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