Challenge 1 - 4, 9, 11, 13, 14, 16, 17, 20, 21 & 23 - 30: SumitKanth
name: Sumit Kanth github_user_name: SumitKanth
URL of my Forked Repository : https://github.com/SumitKanth/scaler-september-open-source-challenge
Screenshot of Cloned Project :

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

Challenge 4: Screenshot showing the latest repository contents


Challenge 9:

Challenge 11:


Challenge 13:

Challenge 14: Process for creating merge conflict


Challenge 16: Conflict in Pull Request


Resolved this merge conflict using local git



Challenge 17: Screenshots of using github desktop:
Created a new repository github_desktop_demo_scaler

Updated README.md

Commit

Pull request


Merging pull request

Challenge 20:




Challenge-21 : Screenshot of alias created and usage of alias

Challenge 23:
Things I understood and found important after going through the resources provided are:
guidelines to follow for issue:
- If you spot a problem search if an issue already exists .If a related issue doesn't exist, new issue can be created using a relevant issue form.
- new issue created should have clear purpose.
- Scan through existing issues to find one that interests you. search can be narrowed using labels as filters like easy difficulty task, question ,etc.
- Comment on it and say you're working on that issue. to avoid conflicts with others also working on the issue.
guidelines to follow for branch creation:
- branch are mostly of two types Regular(permanent bases) & Temporary Branches(fixing or new feature).
- branch name should have a Group word like bug/WIP.
- Unique IDs in branch names.
- Use Hyphen or Slash as Separators for easy reading.
- Branch with Author Name.
- Avoid long descriptive names for branches.
guidelines to follow for pull request:
- Give your commits and PRs descriptive titles.
- meaningful description.
- Show your functionality visually, whenever possible like adding screenshots.
- link PR to issue if you are solving one.
Challenge 24: Search for good first issues to make contributions. Status : Currently looking for issues that I am able to contribute. I explored many issues but most people had listed complex issues that are, as of now, beyond my contributing knowledge. I will soon update this when I find a suitable issue to contribute.
Challenge 25: Search for good first issues to make contributions. Status : Today also I explored many issues but most people had listed complex issues that are, as of now, beyond my contributing knowledge. I will soon update this when I find a suitable issue to contribute. Now currently searching from youtube to contribute in suitable issue.
Challenge 26: Successfully registered in hacktoberfest 2022 :

And regarding the open source contribution, I got an relative issue created by project admin and I comment on that issue that plz assign me for this task, but their were 2-3 more comments above me so now waiting for who will get assigned !
Challenge 27:
Tips to follow for Hacktoberfest :
- Look for the “hacktoberfest” label, repository without “hacktoberfest” label/topic are not considered for the event.
- Total 4 PR/MR should be accepted between 1 oct to 31 oct.
- PR must not be spammy, if 2 spam PR found person is disqualified.
- Search for proper labels according to your knowledge.
- Read the README.md , CONTRIBUTING.md file and follow their guidelines for contributing on that project.
And regarding the open source contribution, not got assigned in the issue. But created new issue in another repo.
Challenge 28:
Current status of contributing to open source is I have created issue and waiting to get assign.

Challenge 29:
Shared a project ideas for Scaler Open Source Projects

Challenge 30:
Finally completed Challenge 24


Milestone -4 done
@Mrjoy832 Thanks