Skip to content
This repository was archived by the owner on Aug 30, 2023. It is now read-only.

Commit 77a6e7e

Browse files
shivaylambacy20001yadav
shivaylamba
authored and
cy20001yadav
committed
parent 2c35807
author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785484 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785483 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785482 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785481 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785480 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785479 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785478 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785477 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785474 +0530 parent 2c35807 author Shivay Lamba <[email protected]> 1662010322 +0530 committer cy20001yadav <[email protected]> 1663785457 +0530 Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> parent 8208c7f author Shivay Lamba <[email protected]> 1662013042 +0530 committer cy20001yadav <[email protected]> 1663332510 +0530 Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Done Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: Chaitanya Yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: Chaitanya Yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: Chaitanya Yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: cy20001yadav <[email protected]> Signed-off-by: Chaitanya Yadav <[email protected]> Signed-off-by: Chaitanya Yadav <[email protected]>
1 parent 2c35807 commit 77a6e7e

28 files changed

+448
-1
lines changed

‎.github/workflows/linter.yaml

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
name: Lint Code Base
2+
3+
on:
4+
push:
5+
branches-ignore: [master, main]
6+
# Remove the line above to run when pushing to master
7+
pull_request:
8+
branches: [master, main]
9+
10+
jobs:
11+
build:
12+
# Name the Job
13+
name: Lint Code Base
14+
# Set the agent to run on
15+
runs-on: ubuntu-latest
16+
17+
##################
18+
# Load all steps #
19+
##################
20+
steps:
21+
##########################
22+
# Checkout the code base #
23+
##########################
24+
- name: Checkout Code
25+
uses: actions/checkout@v3
26+
with:
27+
# Full git history is needed to get a proper list of changed files within `super-linter`
28+
fetch-depth: 0
29+
30+
################################
31+
# Run Linter against code base #
32+
################################
33+
- name: Lint Code Base
34+
uses: github/super-linter@v4
35+
env:
36+
VALIDATE_ALL_CODEBASE: false
37+
DEFAULT_BRANCH: main
38+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

‎CONTRIBUTING.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
## Contributing Guidelines
2+
3+
Thank you for considering contributing to the repository. This guide details all the general information that one should know before contributing to the project.
4+
Please stick as close as possible to the guidelines. That way we ensure that you have a smooth experience contributing to this project.
5+
6+
### General Rules :
7+
These are in general rules that you should be following while contributing to an Open Source project :
8+
9+
- Be Nice, Be Respectful (BNBR)
10+
- Check if the Issue you created, exists or not.
11+
- While creating a new issue make sure you describe the issue clearly.
12+
- Make proper commit messages and document your PR well.
13+
- Always add Comments in your Code and explain it at points, if possible add Doctest.
14+
- Always create a Pull Request from a Branch; Never from the Main.
15+
- Follow proper code conventions because writing clean code is important.

‎Challenges/challenge_1.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
## Welcome to Challenge 1
2+
3+
Welcome to the first challenge!
4+
We will start off with an easy task.
5+
6+
Task:
7+
Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue:
8+
9+
```
10+
name: Add your name here
11+
github_user_name: add your github username here
12+
```

‎Challenges/challenge_10.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
## Welcome to Challenge 10
2+
3+
Welcome to the 10th challenge!
4+
5+
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.
6+
7+
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.
8+
9+
You can read more about how to sign commits [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits)
10+
11+
Task:
12+
1. Setup the ability to sign commits locally in your systems
13+
2. Whenever committing in the future always try to use signed commits
14+
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:
15+
```
16+
---
17+
name: your_name
18+
github_user_name: YOUR-GITHUB-USERNAME
19+
url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge
20+
your_favroite_programming_language: Add your favorite programming language here
21+
---
22+
```

‎Challenges/challenge_11.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
## Welcome to Challenge 11
2+
3+
Welcome to the 11th challenge!
4+
5+
Today's challenge is simple.
6+
7+
Task:
8+
1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main).
9+
2. Share screenshot of this new branch in the issue created in previous challenge

‎Challenges/challenge_12.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
## Welcome to Challenge 12
2+
3+
Welcome to the 12th Challenge
4+
5+
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)
6+
7+
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.
8+
9+
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/
10+
11+
Task:
12+
1. Practice git rebase, and how to squash commit using git rebase in your local projects
13+
2. Once done, try to squash the commits in your pull request in the Challenge repository
14+
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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
## Welcome to Challenge 13
2+
3+
Welcome to the 13th Challenge
4+
5+
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)
6+
7+
Task:
8+
1. Inside the branch you created in the previous challenge ``your-username-details`` create a new file inside the ``contributors/<YOUR-GITHUB_USERNAME>/`` directory.
9+
2. Use the git stash command to move these changes to the stash area
10+
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

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
## Welcome to Challenge 14
2+
3+
Welcome to the 14th Challenge
4+
5+
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.
6+
7+
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.
8+
9+
Task:
10+
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
11+
2. Share appropriate screenshot in the issue created in the first challenge.

‎Challenges/challenge_15.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
## Welcome to Challenge 15
2+
3+
Welcome to the 15th Challenge
4+
5+
In this 2 part challenge, we will try to emulate and fix merge conflicts via git.
6+
7+
Today is the first part of this challenge:
8+
9+
Task:
10+
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
11+
12+
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.
13+
14+
3. Push your change to reflect in the Pull Request created in previous challenges
15+

‎Challenges/challenge_16.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
## Welcome to Challenge 16
2+
3+
Welcome to the 16th Challenge
4+
5+
In this 2 part challenge, we will try to emulate and fix merge conflicts via git.
6+
7+
Today is the second and final part of this challenge:
8+
9+
Task:
10+
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">
11+
12+
2. Try to resolve this merge conflict using local git
13+
14+
3. Once resolved, share screenshot on the github issue created in the previous challenges

‎Challenges/challenge_17.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
## Welcome to Challenge 17
2+
3+
Welcome to the 17th Challenge
4+
5+
Today we will be leaning how to work with GitHub Desktop
6+
7+
#### Brief Overview
8+
9+
GitHub Desktop is a GUI that empowers *lazy* users who prefer not to work with the CLI to still interface with Git and GitHub.
10+
To learn more visit: [What the heck is Git GUI](https://help.github.com/en/desktop/getting-started-with-github-desktop)
11+
12+
13+
## Tasks
14+
15+
- Download GitHub desktop
16+
- Create a new repository on GitHub
17+
- Add anything you want to your repo
18+
- Follow through all the GitHub workflow you know using the GUI (commit, branching, pulling, pushing etc)
19+
- Share a screenshot of your experience using github desktop on the issue created in prior challenges

‎Challenges/challenge_18.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
## Welcome to Challenge 18
2+
3+
Welcome to the 18th Challenge
4+
5+
Today we will be learning to work with GitHub Gist and Markdown
6+
7+
#### Brief Overview
8+
9+
GitHub Gist is two fold and you can either use it for sharing ideas or sharing smaple code. It supports **Markdown**
10+
To learn more, vist:
11+
- [Learn more about GitHub gist](https://help.github.com/en/enterprise/2.13/user/articles/about-gists)
12+
13+
## Task
14+
15+
- Create a gist writing on any software development related topic that interests you
16+
- Create a gist sharing a small code snippet in your preferred programming language
17+
18+
## How to Submit
19+
20+
- Create your submission a markdown file named ``gist-solutions.md`` and add it inside the branch ``your-username-details`` used in previous challenges
21+
- In your submission file add the links to your **2 gist**
22+
- Ensure you push it so that it reflects inside your Pull request created in previous challenges

‎Challenges/challenge_19.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
## Welcome to Challenge 19
2+
3+
Welcome to the 19th Challenge
4+
5+
Today's challenge is unique. Today we will learn about code linting. A linter is defined as follows:
6+
- Lint, or a linter, is a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs.
7+
8+
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.
9+
10+
Task:
11+
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.
12+
2. Commit the change and push it.
13+
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_2.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
## Welcome to Challenge 2
2+
3+
Welcome to the second challenge!
4+
Today we will focus on how to fork and create a clone of a Github repository
5+
6+
Task:
7+
1. Create a fork of this repository
8+
2. Clone the forked project locally in your system using the ``git clone`` command
9+
3. 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:
10+
- URL of your forked repository
11+
- A screenshot of the cloned project in your system

‎Challenges/challenge_20.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## Welcome to Challenge 20
2+
3+
Welcome to the 20th Challenge
4+
5+
Today you will learn about project boards on GitHub
6+
7+
### What are Github Project Boards?
8+
9+
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)
10+
11+
## Tasks
12+
13+
- Create a GitHub repository for any project you can think up
14+
- On a sheet of paper create a TODO list (or backlog) of features you want to have in you app
15+
- Create a project board with a `TODO` column, `In progress`, `Done`
16+
- Create a card for all the items you already wrote on the sheet of paper in the TODO column
17+
- Work on the features synchronously and move the card respectively for each in progress task to the `In progress` column
18+
- When you're done with the `In progress` task move the card to the `Done` column
19+
20+
## How to submit your entry
21+
22+
- Take a screenshot of your project board for when you moved an card from `In progress` to `Done`
23+
- Add you screenshot to the Github issue created in the previous challenges

‎Challenges/challenge_21.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
## Welcome to Challenge 21
2+
3+
Welcome to the 21st Challenge
4+
5+
Today we will be learning about Git Aliases! :). This is an amazing feature that helps us use less keystroke
6+
7+
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;
8+
9+
- [Git Alias](https://www.atlassian.com/git/tutorials/git-alias)
10+
11+
## Tasks
12+
13+
- Go through the Git Alias documentation shared here
14+
- Create at least 2 alias for any git commands you feel is too long
15+
- Take a screenshot of the alias you created. hint run `git config --get-regexp alias`
16+
- Take a screenshot of using your alias
17+
- Post these screenshot in the issue created in the prior challenges

‎Challenges/challenge_3.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
## Welcome to Challenge 3
2+
3+
Welcome to the third challenge!
4+
Today we will focus on how to create a new branch in a git repository
5+
6+
Task:
7+
1. Following up on the [previous task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_2.md), create a new branch locally in your forked clone repository
8+
2. The branch name should be as follows: ``your_github_username-details``. Example: ``shivaylamba-details``
9+
3. 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:
10+
- Screenshot showing the list of all the current branches inside of your forked clone repository

‎Challenges/challenge_4.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
## Welcome to Challenge 4
2+
3+
Welcome to the fourth challenge!
4+
Today we cover how to Update Fork Repo From the Original Repo
5+
6+
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``
7+
8+
Task
9+
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
10+
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:
11+
- Screenshot showing the latest repository contents

‎Challenges/challenge_5.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
## Welcome to Challenge 5
2+
3+
Welcome to the fifth challenge!
4+
Today's goal is to update your forked repository and then create a Pull Request
5+
6+
Task
7+
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
8+
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.
9+
10+
```
11+
contributors/shivaylamba/
12+
```
13+
14+
3. Create a markdown file in the folder you created following the naming convention for the file: `<YOUR-GITHUB-USERNAME>.md`. Ex.
15+
16+
```
17+
contributors/shivaylamba/shivaylamba.md
18+
```
19+
20+
4. Copy the following template into your file, delete the placeholder text and fill the information with yours.
21+
22+
```
23+
---
24+
name: your_name
25+
github_user_name: YOUR-GITHUB-USERNAME
26+
---
27+
```
28+
5. Submit your Pull Request on the main challenge repo.

‎Challenges/challenge_6.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
## Welcome to Challenge 6
2+
3+
Welcome to the sixth challenge!
4+
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)
5+
6+
Task
7+
1. Create a new commit in the branch you created in Challenge 2 in your forked repository
8+
2. The change that you have to make should be the following:
9+
In the markdown file that was created in Challenge 5, edit the details as follows:
10+
```
11+
---
12+
name: your_name
13+
github_user_name: YOUR-GITHUB-USERNAME
14+
url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge
15+
---
16+
```
17+
3. After making this change create a commit with a proper commit message and push the changes
18+
4. Check if the commit reflects in the Pull request you created in Challenge 5
19+

‎Challenges/challenge_7.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
## Welcome to Challenge 7
2+
3+
Welcome to the seventh challenge!
4+
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.
5+
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.
6+
So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge.
7+
8+
Task:
9+
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

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
## Welcome to Challenge 8
2+
3+
Welcome to the 8th challenge!
4+
5+
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.
6+
7+
8+
Task:
9+
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
10+
11+
2. Ensure the change appears in the Pull request created in previous challenges

‎Challenges/challenge_9.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
## Welcome to Challenge 9
2+
3+
Welcome to the ninth challenge!
4+
5+
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).
6+
7+
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.
8+
9+
This can be done by using the following command: ``git reset``
10+
11+
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.
12+
13+
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.
14+
15+
16+
Task:
17+
1. Identify the commit id that needs to be removed (you should have created this in the 8th Challenge)
18+
2. Use git reset and force push, to remove the commit from your pull request.
19+
3. Share a screenshot of this, in the issue you created in previous challenges.

0 commit comments

Comments
 (0)