Challenge - 1,2,3,4,9,11,13,14,16,17,20,21,23,24,25,26,27,28,29,30 : Kura Akhilesh

[kuraakhilesh8230]

name: Kura Akhilesh github_user_name : kuraakhilesh8230

[kuraakhilesh8230]

URL of forked repository : https://github.com/kuraakhilesh8230/scaler-september-open-source-challenge Screenshot of clone :

[kuraakhilesh8230]

Screenshot showing the list of all the current branches inside of forked clone repository :

[kuraakhilesh8230]

Screenshot showing the latest repository contents :

[kuraakhilesh8230]

challenge : 9

[kuraakhilesh8230]

Challenge 11 : Created another branch from current branch

[kuraakhilesh8230]

challenge-13 : Used git stash command

[Mrjoy832]

✅ Good to go😎🤩

[kuraakhilesh8230]

challenge-14 : reproduced a case of merge conflict in system for a project tried to resolve it

[kuraakhilesh8230]

Challenge-16 : Conflict in pull request resolved this merge conflict using local git No conflict in pull request

[kuraakhilesh8230]

challenge-17: use github desktop

[kuraakhilesh8230]

Challenge-20 : Working with GitHub Project Boards

Repository Link Project Board Link

[kuraakhilesh8230]

Challenge-21 : Screenshot of alias created

Screenshot of using alias

[kuraakhilesh8230]

Challenge-23 :

PR{s)

1. Write descriptive and consistent names
2. Create a clear PR title and description
3. Keep PRs short (same applies to files and functions)

Branch(s)

1. The important branches in any project is the -Main - Stable version -Development - Where all the changes take place -QA - Where all the testing takes place
2. The branches we will be working on has to be named as per a standard. For example, the branch name can include words like bug, fix, WIP, etc, the issue it will be solving, author name, etc.
3. The name of these branches should match with the naming convention of the rest of the team.

Issue(s)

1. Always see for good-first-issue in the repos
2. Avoid long descriptive names
3. Create only meaningful issues

[kuraakhilesh8230]

Challenge-24 : I have been assigned 4 issues

• Breath First search Algorithm
• Depth First Search Algorithm
• Inorder tree traversal algorithm
• post tree traversal algorithm

[kuraakhilesh8230]

challenge-25: I have been assigned 4 issues and I have started working upon them and will make a PR for them asap

• Breath First search Algorithm
• Depth First Search Algorithm
• Inorder tree traversal algorithm
• post tree traversal algorithm -Hello world program That's it for today!!

[DaltonDeven]

Verified for Milestone-3 Congratsss

[kuraakhilesh8230]

Verified for Milestone-3 Congratsss

Tq

[kuraakhilesh8230]

Challenge-26 : Successfully registered in hacktoberfest 2022 and here is the screenshot :

Regarding the issues I'm working on I have been assigned 4 issues and I am started to work on it and will update here after got merged

That's it for today!!!

[kuraakhilesh8230]

Challenge- 27 : Tips on Hacktoberfest-2022 when participating :

HERE’S WHAT YOU NEED TO KNOW TO PARTICIPATE AND COMPLETE HACKTOBERFEST :

-Register anytime between September 26 and October 31 -Pull requests can be made in any GITHUB or GITLAB hosted project that’s participating in Hacktoberfest (look for the “hacktoberfest” topic) -Project maintainers must accept your pull/merge requests for them to count toward your total -Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest -The first 40,000 participants (maintainers and contributors) who complete Hacktoberfest can elect to receive one of two prizes: a tree planted in their name, or the Hacktoberfest 2022 t-shirt.

RESOURCES FOR BEGINNERS : INTRO TO OPEN SOURCE :

-DigitalOcean: INTRODUCTION TO GITHUB AND OPEN-SOURCE PROJECTS

-GitHub: HOW TO CONTRIBUTE TO OPEN SOURCE

-DigitalOcean: WHAT IS OPEN SOURCE

-DigitalOcean: HOW TO USE GIT

HERE’S HOW WE VALIDATE CONTRIBUTOR PULL/MERGE REQUESTS (“PR/MRS”) FOR HACKTOBERFEST :

-YOUR PR/MRS MUST BE WITHIN THE BOUNDS OF HACKTOBERFEST. -REPOS THAT GO AGAINST HACKTOBERFEST’S VALUES WILL BE EXCLUDED FROM QUALIFICATION AND PR/MRS MADE TO THOSE REPOS WON’T COUNT. -YOUR PR/MRS MUST NOT BE SPAMMY. -YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR BE LABELED “HACKTOBERFEST-ACCEPTED.” -YOUR PR/MRS MUST NOT BE LABELED AS “INVALID”. -YOUR PR/MRS MUST BE MERGED, HAVE THE “HACKTOBERFEST-ACCEPTED” LABEL, OR HAVE AN OVERALL APPROVING REVIEW. -ONCE YOUR PR/MRS PASS ALL THE CHECKS ABOVE, IT WILL BE ACCEPTED FOR HACKTOBERFEST AFTER THE 7-DAY REVIEW PERIOD.

MEASURES TO REDUCE SPAM :

-SPAMMY PULL/MERGE REQUESTS WILL BE LABELED AS “SPAM.” -PULL/MERGE REQUESTS MUST BE APPROVED BY A MAINTAINER. -BAD REPOSITORIES WILL BE EXCLUDED. -AVOID SUBMITTING LOW-QUALITY PULL/MERGE REQUESTS.

[kuraakhilesh8230]

Challenge-28 :

Current status of contributing to open source

Following are the Pull Request created and successfully Merged: Added hello world program

[kuraakhilesh8230]

Challenge- 29

Upvoted ideas : Student Progress Tracker #109

Portfolio Generator #45

My Project idea discussion links :

First Contributions #118

[kuraakhilesh8230]

Challenge 30 :

Finally the day came which is the end of 30 days of scaler open source challenge 2022 and I want to share my experience in this whole journey and talking about it I had an amazing experience in this by learning about git , github and how to contribute to open source projects.

Before this i haven't had a experience of this github and now i learned so much about what exactly is this git , github and why so many people will use this github.

I want to say a big thank you to all the community members especially @shivaylamba sir for sharing his amazing knowledge about open source and giving opportunities to others to learn about this and also @dmanocha464 also for helping me when ever I stuck somewhere.

This is not the end of this open source journey of mine because next month HACKTOBERFEST is also going to start and I am hoping I will contribute to the open source projects and complete that also successfully as that will be my first time participation.

Finally I want to say a big thank you to scaler also for hosting this amazing challenge

That's it !!!!

[Mrjoy832]

Milestone-4 done ✅

[kuraakhilesh8230]

Milestone-4 done ✅

Thank you @Mrjoy832 😊