Scaler September Challenge

[just-injoey]

name: Justin T Joseph github_user_name: just-injoey

[just-injoey]

URL: https://github.com/just-injoey/scaler-september-open-source-challenge Screenshot:

[just-injoey]

Screenshot showing the required branch inside forked clone repository :

[just-injoey]

Screenshots showing the latest repository contents in both branches:

[just-injoey]

Updated contributors directory:

[just-injoey]

Challenge 6 - Updated Contributors directory

[just-injoey]

Challenge 7:

[just-injoey]

Challenge 8:

[just-injoey]

Challenge 9:

[just-injoey]

Challenge 10:

[just-injoey]

Challenge 11:

[just-injoey]

Challenge 12:

[just-injoey]

Challenge 13:

[just-injoey]

Challenge 14:

[just-injoey]

Chalenge 15:

[just-injoey]

Challenge 16:

[just-injoey]

Challenge 17:

1. Installed GitHub Desktop
2. Create a new branch
3. Edit a file
4. Make a commit
5. Publish to GitHub 6.Open a pull request

[just-injoey]

Challenge 18:

[just-injoey]

Challenge 19:

[just-injoey]

Challenge 20:

1. Created Project Board and added tasks to the TODO column
2. Added a task to In Progress column
3. Moved the tasks from In Progress column to the Done column
4. Finally moved all the tasks In Progress column to the Done column

Linked Repository Countdown-Timer

[just-injoey]

Challenge 21:

[just-injoey]

Challenge 22:

[just-injoey]

Challenge 23:

1. First find Issue - We can find the issues by using these tags

   1. [issues labeled good first issue]
   2. [issues labeled help wanted]
   3. [PRs labeled help wanted]

2. Issue

   1. issue created should have clear purpose.
   2. Avoid long descriptive names.
   3. Comment on it and say you're working on that issue. to avoid conflicts with others while also working on the issue.
   4. Create issues that are meant for us.

3. Branch:

   1. The branches created should have clear name
   2. Branching with the author name makes it easier for us to filter out our own branches

4. Pull Request:

   1. Give your commits and PRs active and descriptive titles
   2. Streamline your process of creating a new PR
   3. Give your PR a meaningful description
   4. Show your functionality visually, whenever possible
   5. Review your own PR before you assign it to others

5. Submit PR and wait for code review and address any issues raised as soon as you can.

[just-injoey]

Challenge 24: Status : Currently I am still looking for issues that I am able to contribute. I will soon update this when I find a suitable issue to contribute.

[just-injoey]

Challenge 25: Status : I am still looking for issues. I will soon update this when I find a suitable issue to contribute.

[just-injoey]

Challenge 26: Status : I have registered for Hacktoberfest, I am still looking for issues. I will soon update this when I find a suitable issue to contribute.

[DaltonDeven]

Challenge 25 pending, contribute and update you PR soon to be eligible for milestone-3

[just-injoey]

Challenge 27:

Tips for hacktoberfest:

1. Firstly we have to get assigned to an issue which is assigned by a maintainer of the issue.
2. We have create a pull request and it's should be accepted and merged by maintainer.
3. “HACKTOBERFEST” topic must be tagged in our PR of repo.
4. Don't make any spam or any type violance if do the person will blocked.
5. Deadline for this:Oct1-Oct30 will count only.
6. We have to creatE 4 PR between the deadlines.

[just-injoey]

Challenge 25 pending, contribute and update you PR soon to be eligible for milestone-3

I will soon be doing it.

[just-injoey]

Challenge 28: Status: I got assigned to an issue and I have started working on it.

[DaltonDeven]

Verified for milestone-3 congrats...