scaler open source sep challenges

[krishu45]

name: krishang gupta github_user_name:krishu45

[krishu45]

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

[krishu45]

challenge 3

[krishu45]

[krishu45]

[krishu45]

[krishu45]

[krishu45]

[krishu45]

[krishu45]

challenge 17 link to repistory

[krishu45]

day 20

[krishu45]

challenge 21

[kuraakhilesh8230]

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

[krishu45]

challenge 23

An overview of what I learned from reading those articles are as follows: Branches -> Every project has crucial branches, and these are the ->Main/Master-Default branch and stable branch ->Development is the area where all the changes are made, and it is kept distinct from the main branch. ->QA is where all of the testing is done. ->These branches' names ought to follow the team's overall naming scheme. The branch name may contain terms like "bug fix," "work in progress," "problem it will resolve," "author name," etc.

Issues:- ->We may identify issues related to our interests by using labels, which also helps us determine whether the problem is something we can work on. -->If we want to make some modifications that are not described in any issues, we must create a new issue indicating what we want to modify with an appropriate description. Excellent-first-issues labels are typically a good place to start for someone new to open source.

Pull Request:- ->Suitable naming should be used ->Writing suitable commit messages and PR descriptions is important. ->They should have a descriptive titles ->We should review our PR before assigning to others

[krishu45]

challenge 24 I tried to find some issue which i can work for but couldnt

[krishu45]

challenge 25 I again tried looking some issue at my level but unavle to find but maybe i and my friends found something whixh we could use tommorow

[krishu45]

challenge 26 Maybe i found some project but looking fir someoene to help me in coding bcz i dont k ow coding yet

[krishu45]

Challenge 27 :-

Registered for hectoberfest

Some Guidelines for Contributors in Hacktoberfest 2022 :-

PULL/MERGE requests :-

Every PR must be made public and should be created between October 1 to October 31.

Any low quality PR won't count.

Contributors should not spam any PRs in any hacktoberfest repo. (any pr labeled invalid or spam will not be counted for contribution)

PRs must be tagged with Hackertoberfest-Accepted.

Also u can find more repos in thier discord

[krishu45]

challeng 28 I formed team with some members but we are finding repo which are easy Also i dint know any coding so findig repo is more tough

[krishu45]

Challenge 29:- UPVOTED some ideas that I liked from

[krishu45]

Challenge 30:

Finally, the day came which is the end of 30 days of scaler open source challenge 2022. I had an amazing experience in this by learning about git, GitHub, and how to contribute to open source projects. Thanks for conducting this challenge - A challenge where there is nothing to lose only your knowledge in the field of GitHub will increase. 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.

[Mrjoy832]

Milestone-4 done ✅