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

Commit 7d12751

Browse files
committed
Revert "Initial commit, squashed all the commits"
This reverts commit b85b6fe. Initial commit Update details Update README.md Make final update to ReadME Create CONTRIBUTING.md Add Challenge 1 Update challenge_1.md Update challenge_1.md Create challenge_2.md Create challenge_3.md challenge 4 Challenge 5 Update challenge_5.md Update challenge_5.md Create challenge_6.md Update challenge_6.md Create challenge_7.md Create challenge_8.md Update challenge_8.md Create challenge_9.md Create challenge_10.md a new commit Signed-off-by: Kinshuk2003 <kinshukgoyal2003@gmail.com>
1 parent 4f262b1 commit 7d12751

File tree

5 files changed

+56
-3
lines changed

5 files changed

+56
-3
lines changed

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

contributors/Kinshuk2003-2.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
hi i am kinshuk goyal a competitive programmer
Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
name: Kinshuk Goyal
3-
4-
github_user: Kinshuk2003
3+
github_user_name: Kinshuk2003
54
url_of_github_issue: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/205
6-
---
5+
your_favroite_programming_language: C, C++, Python, HTML, CSS, JAVASCRIPT
6+
---

0 commit comments

Comments
 (0)