Merge branch 'main' into sreejasaha19-details

Author: sreejasaha19

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

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

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

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

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. 

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 

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

contributors/sreejasaha19/gist-solutions.md

@@ -0,0 +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
+---

contributors/sreejasaha19/temp.md

@@ -0,0 +1 @@
+