Challenge (30/30) : anishcode19

[anishcode19]

name: Anish Kumar github_user_name: anishcode19

[anishcode19]

https://github.com/anishcode19/scaler-september-open-source-challenge

[anishcode19]

[anishcode19]

[anishcode19]

![Uploading day-9.png…]()

[anishcode19]

[anishcode19]

[anishcode19]

[anishcode19]

[anishcode19]

[anishcode19]

[anishcode19]

Challenge 23 : Summary

Branches

• Broadly, git branches are divided into two categories: Regular & Temporary Branches.
• Regular Branches : There should be 3 permanent base branch - master , development and QA. The names signifies their purpose.
• Start branch name with a Group word : By looking at the branch name, can understand what this Git branch is about and its purpose.
• For example : while fixing a bug, the syntax should be --> group_tag-<your_branchName>
• Using tracker ID in a branch would be ideal way to track the working tree .
• Using of the / as separators increases the readability and avoid confusion.
• You can add your name to the branch to signify your bug fixes.
• Note : avoid using long names , which might increase confusion".

Issue

Issues available for community contribution:

• The following tags mark issues that are open for community contribution:
• Help wanted: Open to participation from the community but not necessarily beginner-friendly.
• good first issue: Open to participation from the community and friendly towards new contributors.

Issues not available for community contribution:

• The following tags mark issues that are not open for community contribution:
• staff only: Requires infrastructure access or institutional knowledge that would be impractical to provide to the community

Issues not ready for work:

• The following tags mark issues that are not open for community contribution:
• Status: Blocked: Blocked by other work that needs to be done first
• Status: Ticket work required: Needs additional work before it is ready to be taken up
• Status: Awaiting triage: Has not been triaged by a maintainer

Issues without any of the above labels:

• These issues may (or may not) be open for contribution.
• Please add a comment asking one of the maintainers to triage the issue and label it as appropriate.

Pull Request

• Give your feature branch a clear name.
• Give your commits and PRs descriptive titles.
• Show your functionality visually, whenever possible like adding screenshots.
• Show your functionality visually, whenever possible.

[anishcode19]

Challenge-24

Still looking for a GitHub repo to find relevant issues where I could actually contribute but didn't find any for now. I will continue looking and possibly find one that I can actually solve.

[anishcode19]

I explored many repository issues and commented on 1 -2 issues for approval or assignment. I will update my work.

[anishcode19]

Challenge- 25

I have been assigned 2 issues and I have started working on them and will make a PR for them asap

• https://github.com/PrakashGatiyala/60-seconds-of-cpp/issues/2#issue-1385080010
• https://github.com/Ashutosh00710/github-readme-activity-graph/issues/25#issuecomment-1257155609

That's it for today!!

[anishcode19]

Challenge- 26

I have registered for Hacktoberfest and I got the Hacktoberfest 2022: Registered badge from Hacktoberfest! https://www.holopin.io/claim/cl8j3tc30828609kzv27v472k

[kuraakhilesh8230]

congrats you have completed milestone-3 successfully and you are good to go🎉

[anishcode19]

Challenge 27

• I already registered for Hacktoberfest
• I am participating as a contributor and maintainer for this Hacktoberfest 2022.

Tips

• For PRs to be counted into your participation in Hacktoberfest, they must be merged between October 1st and October 31st.
• As a beginner, try contributing to documentation issues like updating links, renaming, etc. This will give you an idea about open source contribution, forking repo, Pull request, PR merge, etc.
• We need to submit at least four PRs to complete Hacktoberfest.
• Project maintainers must accept our pull/merge requests for them to count toward our total.
• We need to follow the Hacktoberfest guidelines and rules thoroughly.
• Contributions must be made to public repositories.

Some repositories for Contribution

• GoodFirstIssues.com
• GoodFirstIssue.dev

[anishcode19]

Challenge 28

I have created a pull request for one of the issues that I was assigned. I contributed to 1 good first contributions now:

One of my PRs got merged successfully into the project. Also Reading some repository contribution guidelines.

Also, clone the repository of 60 seconds of code in C++ and trying to contribute more to this repo.

[anishcode19]

Challenge 29

Ideas that I liked :

1. CSS Generator
2. Real-time Chat App💌
3. Real Time Code Plagiarism and Contestant Removal

My opened Discussion link -

Virtual Travel guide

[anishcode19]

Challange 30

Successfully completed all the challenges. Thanks to Scaler for organizing it, everyone in the community was helpful and encouraged a lot during these 30 days. It was a great learning experience with Scaler Open-Source. As I was a beginner to GitHub so I didn't have even the basic knowledge of using GitHub, but due to these challenges only I was able to learn and understand many new and important things. Lastly, I will continue my journey of open source, really excited about Hactoberfest as this will be the first time I will participate.

[Mrjoy832]

Milestone-4 done ✅