Merge branch 'main' into subhashjain010-details

.github/workflows/linter.yaml

@@ -35,4 +35,7 @@ jobs:
         env:
           VALIDATE_ALL_CODEBASE: false
           DEFAULT_BRANCH: master
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          DEFAULT_BRANCH: main
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+

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 

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 

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 

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 

challengers-list.md

@@ -1,4 +1,5 @@
 # List of challengers
 1. [Mrinal](https://github.com/mrinal1224)
 2. [Shivay](https://github.com/shivaylamba)
-3. [Subhash Jain](https://github.com/subhashjain010)
+3. [Raghav](https://github.com/raghavdhingra)
+4. [Subhash Jain](https://github.com/subhashjain010)