Challenge 1 - 4, 9, 11, 13, 14, 16, 17, 20, 21, 23 - 30

[shivambeenhere]

name: Shivam Kumar github_user_name: shivambeenhere

[shivambeenhere]

URL of my Forked Repo : https://github.com/shivambeenhere/scaler-september-open-source-challenge

Screenshot of my cloned project :

[shivambeenhere]

Challenge 3. Screenshot of all the current branches inside my forked clone repository:

[shivambeenhere]

Challenge 4 : Screenshots showing new repo contents :

[shivambeenhere]

Challenge 9 Screenshot : (Challenge 8 commit removed)

[shivambeenhere]

Challenge 11 : Created new branch

[shivambeenhere]

Challenge 13 : Stash File

[Mrjoy832]

All good ✅

[shivambeenhere]

Challenge 14 : Practice resolving merge conflicts

[shivambeenhere]

Challenge 16 : Merge Conflict Fixed

[shivambeenhere]

Challenge 17 : Github Desktop

Created dektop-tutorial Repo : Created new branch : Updating readme : Committing changes : Pushing changes to remote repo : Pull request created :

• Easy and convenient to use

[shivambeenhere]

Challenge 20 : Created Project Board Repo Link : https://github.com/shivambeenhere/Sorting-Visualizer Project Board : https://github.com/users/shivambeenhere/projects/1/views/1

[shivambeenhere]

Challenge 21 : Using alias

[Mrjoy832]

Milestone-2 done✅

[shivambeenhere]

Challenge 23 :

Branches:

• Main/Master-Default and stable branch are important branches.
• The branch name can include a bug, fix, WIP, the issue it will solve, author name, etc.
• Don't use too long descriptive names.
• Use unique id's in branch name.

Issues:

• Always create a new issue, if you have some new idea, stating what we want to change with a proper description.
• Use labels to check status of the issue.
• Good-first-issue labels are a suitable for beginner's in open source contribution.
• Notify others that you are working on the issue by comments, it will decrease conflicts b/w contributors.

Pull Request:

• Write appropriate commit messages and PR descriptions.
• Keep PR short.
• Give your PR a descriptive title.
• Always review your PR before assigning it.

[shivambeenhere]

Challenge 24 : Currently exploring for issues on which I can contribute. Looked up many issues but I was not familiar with any of them. I'm actively searching and will update here.

[shivambeenhere]

Challenge 25 :

Opened my first PR and got it merged. Started off with this because I couldn't find any issue I was comfortable with. I will continue to explore through different projects and will update here.

[shivambeenhere]

Challenge 26 :

Waiting for Hacktoberfest to open registrations. Currently exploring for issues on which I can contribute. Looked up many issues but I was not familiar with any of them. I'm actively searching and will update here.

[shivambeenhere]

Challenge 27 : Registered for Hacktoberfest

Tips for Hacktoberfest :

• Your PR/MRS must be in a repo tagged with the “HACKTOBERFEST” topic, or be labeled “HACKTOBERFEST-ACCEPTED.”
• Don't make spam/low-quality PRs just for the goodies.
• Only PRs made between Oct 1 - 31 count toward hacktoberfest progress.

[shivambeenhere]

Challenge 28 :

Still looking for other projects I can contribute on apart from the basic PR I made earlier.

[shivambeenhere]

Challenge 29 :

I liked these projects ideas :

• Programming Club Discussion Website for College Students
• A telegram bot that sends customized job opening notifications.
• Real time Chat App

[shivambeenhere]

Challenge 30 :

Happy to share that I have finally completed the challenge. All thanks to Scaler for organizing this event, I got to learn git basics. Going forward I will try to learn some tools and tech stack so that I can contribute to more open source projects. Thanks again Scaler.

[Mrjoy832]

Milestone-4 done ✅