Squashed all commit

shivaylamba · sj5027052 · commit 3a08f476dab2 · 2022-09-23T19:15:13.000+05:30
Signed-off-by: Sanyam Jain &lt;sj5027052@gmail.com&gt;
diff --git a/.github/workflows/linter.yaml b/.github/workflows/linter.yaml
@@ -0,0 +1,38 @@
+name: Lint Code Base
+
+on:
+  push:
+    branches-ignore: [master, main]
+    # Remove the line above to run when pushing to master
+  pull_request:
+    branches: [master, main]
+
+jobs:
+  build:
+    # Name the Job
+    name: Lint Code Base
+    # Set the agent to run on
+    runs-on: ubuntu-latest
+
+    ##################
+    # Load all steps #
+    ##################
+    steps:
+      ##########################
+      # Checkout the code base #
+      ##########################
+      - name: Checkout Code
+        uses: actions/checkout@v3
+        with:
+          # Full git history is needed to get a proper list of changed files within `super-linter`
+          fetch-depth: 0
+
+      ################################
+      # Run Linter against code base #
+      ################################
+      - name: Lint Code Base
+        uses: github/super-linter@v4
+        env:
+          VALIDATE_ALL_CODEBASE: false
+          DEFAULT_BRANCH: main
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/Challenges/challenge_10.md 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
@@ -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
@@ -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
@@ -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
diff --git a/Challenges/challenge_14.md b/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. 
diff --git a/Challenges/challenge_15.md b/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
+
diff --git a/Challenges/challenge_16.md b/Challenges/challenge_16.md
@@ -0,0 +1,14 @@
+## Welcome to Challenge 16
+
+Welcome to the 16th Challenge 
+
+In this 2 part challenge, we will try to emulate and fix merge conflicts via git. 
+
+Today is the second and final part of this challenge: 
+
+Task: 
+1. You will notice that your pull request will have a conflict: <img width="636" alt="image" src="https://user-images.githubusercontent.com/19529592/190574995-0cc506a8-a2fe-4aa4-98bd-4658e8aa2fc1.png">
+
+2. Try to resolve this merge conflict using local git 
+
+3. Once resolved, share screenshot on the github issue created in the previous challenges
diff --git a/Challenges/challenge_17.md b/Challenges/challenge_17.md
@@ -0,0 +1,19 @@
+## Welcome to Challenge 17
+
+Welcome to the 17th Challenge 
+
+Today we will be leaning how to work with GitHub Desktop
+
+#### Brief Overview
+
+GitHub Desktop is a GUI that empowers *lazy* users who prefer not to work with the CLI to still interface with Git and GitHub.
+To learn more visit: [What the heck is Git GUI](https://help.github.com/en/desktop/getting-started-with-github-desktop)
+
+
+## Tasks
+
+- Download GitHub desktop
+- Create a new repository on GitHub
+- Add anything you want to your repo
+- Follow through all the GitHub workflow you know using the GUI (commit, branching, pulling, pushing etc)
+- Share a screenshot of your experience using github desktop on the issue created in prior challenges
diff --git a/Challenges/challenge_18.md b/Challenges/challenge_18.md
@@ -0,0 +1,22 @@
+## Welcome to Challenge 18
+
+Welcome to the 18th Challenge 
+
+Today we will be learning to work with GitHub Gist and Markdown
+
+#### Brief Overview
+
+GitHub Gist is two fold and you can either use it for sharing ideas or sharing smaple code. It supports **Markdown**
+To learn more, vist:
+- [Learn more about GitHub gist](https://help.github.com/en/enterprise/2.13/user/articles/about-gists)
+
+## Task
+
+- Create a gist writing on any software development related topic that interests you
+- Create a gist sharing a small code snippet in your preferred programming language
+
+## How to Submit
+
+- Create your submission a markdown file named ``gist-solutions.md`` and add it inside the branch ``your-username-details`` used in previous challenges
+- In your submission file add the links to your **2 gist**
+- Ensure you push it so that it reflects inside your Pull request created in previous challenges
diff --git a/Challenges/challenge_19.md b/Challenges/challenge_19.md
@@ -0,0 +1,13 @@
+## Welcome to Challenge 19
+
+Welcome to the 19th Challenge 
+
+Today's challenge is unique. Today we will learn about code linting. A linter is defined as follows: 
+- Lint, or a linter, is a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs. 
+
+So in order to ensure proper codestyling and structure, there are checks run on pull requests to ensure the code is properly linted. We have also placed a code linter Github action which will keep a track whether your code is properly linted or not. 
+
+Task: 
+1. Create a new file inside your branch created in previous challenges ``your-username-details`` under the directory ``contributors/username``. The file needs to be a source code file written in your preferred programming language. The code can be anything you want: hello world program or your favorite program. 
+2. Commit the change and push it. 
+3. Check if your linting fails in side the Pull request: <img width="870" alt="image" src="https://user-images.githubusercontent.com/19529592/190969615-f3205b26-83eb-4b5f-b7a5-19567a575a9a.png"> <br> Then lint your code to ensure that this check passes inside your pull request. 
diff --git a/Challenges/challenge_20.md b/Challenges/challenge_20.md
@@ -0,0 +1,23 @@
+## Welcome to Challenge 20
+
+Welcome to the 20th Challenge 
+
+Today you will learn about project boards on GitHub
+
+### What are Github Project Boards?
+
+GitHub project boards helps you keep track of stuffs you're actively working on within your repository. You can say it's a project managemnet tool, or even a collaboration tool for teams. You create a project board with columns for your TODO or backlogs or even bugs, In progress activies and lastly a column for your finished tasks. You can sort of see it as a SCRUM board. To learn more [about project boards go through this link](https://help.github.com/en/github/managing-your-work-on-github/about-project-boards)
+
+## Tasks
+
+- Create a GitHub repository for any project you can think up
+- On a sheet of paper create a TODO list (or backlog) of features you want to have in you app
+- Create a project board with a `TODO` column, `In progress`, `Done`
+- Create a card for all the items you already wrote on the sheet of paper in the TODO column
+- Work on the features synchronously and move the card respectively for each in progress task to the `In progress` column
+- When you're done with the `In progress` task move the card to the `Done` column
+
+## How to submit your entry
+
+- Take a screenshot of your project board for when you moved an card from `In progress` to `Done`
+- Add you screenshot to the Github issue created in the previous challenges 
diff --git a/Challenges/challenge_21.md b/Challenges/challenge_21.md
@@ -0,0 +1,17 @@
+## Welcome to Challenge 21
+
+Welcome to the 21st Challenge 
+
+Today we will be learning about Git Aliases! :). This is an amazing feature that helps us use less keystroke
+
+ The term alias is synonymous with a shortcut. Alias creation is a common pattern found in other popular utilities like `bash` shell. Aliases are used to create shorter commands that map to longer commands. Aliases enable more efficient workflows by requiring fewer keystrokes to execute a command. To learn more;
+
+ - [Git Alias](https://www.atlassian.com/git/tutorials/git-alias)
+
+  ## Tasks
+
+ - Go through the Git Alias documentation shared here
+ - Create at least 2 alias for any git commands you feel is too long
+ - Take a screenshot of the alias you created. hint run `git config --get-regexp alias`
+ - Take a screenshot of using your alias
+ - Post these screenshot in the issue created in the prior challenges 
diff --git a/Challenges/challenge_22.md 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 
diff --git a/Challenges/challenge_23.md b/Challenges/challenge_23.md
@@ -0,0 +1,22 @@
+## Welcome to Challenge 23
+
+Welcome to the 23rd Challenge 
+
+So far all of you have learnt the basics of Git and Github. 
+Now let's move to the next step and actually start contributing to real open source projects but before we do that it is super important to go through the contributing guidelines for that project. 
+
+Most projects either come with a ``CONTRIBUTING.md`` file or might have details on how to make contributions to a project, whether it is through creation of an issue, or creating a Pull Request. 
+
+A Sample ``CONTRIBUTING.md`` file can be found [here](https://github.com/github/docs/blob/main/CONTRIBUTING.md), 
+
+Here are some resources for good practices for git branch naming conventions, pull request creation and issue triaging: 
+1. https://codingsight.com/git-branching-naming-convention-best-practices/
+2. https://tighten.com/blog/building-a-great-pull-request/
+3. https://opensource.creativecommons.org/contributing-code/
+4. https://youtu.be/8wt-8B9vCQg
+
+
+Task: 
+Today's task is simple but super important, go through all these links, and summarize what you learn about what needs to be done for effective open source contribution, especially with respect to open source issue creation, best practices around branch/pull request creation. 
+
+Add this as a comment in the issue created in prior challenges 
diff --git a/Challenges/challenge_4.md 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
diff --git a/Challenges/challenge_5.md 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/<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.
diff --git a/Challenges/challenge_6.md 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
@@ -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
@@ -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
diff --git a/challengers-list.md b/challengers-list.md
diff --git a/contributors/shivaylamba/shivaylamba.md b/contributors/shivaylamba/shivaylamba.md
diff --git a/contributors/subhashjain010/gist-solutions.md b/contributors/subhashjain010/gist-solutions.md
diff --git a/contributors/subhashjain010/subhashjain010.md b/contributors/subhashjain010/subhashjain010.md
diff --git a/contributors/subhashjain010/sum_of_digits.py b/contributors/subhashjain010/sum_of_digits.py
