Challenge 1

[kaushalRTJ]

name: kaushal github_user_name: kaushalRTJ

[kaushalRTJ]

Fork URL : https://github.com/kaushalRTJ/scaler-september-open-source-challenge.git

[kaushalRTJ]

Challenge 3

[kaushalRTJ]

Challenge 4

[kaushalRTJ]

challenge 11

[kaushalRTJ]

Challenge 13

[kaushalRTJ]

Challenge

[kaushalRTJ]

Challenge 16

[kaushalRTJ]

Challenge 17

[kaushalRTJ]

Challenge 20

[kaushalRTJ]

Challenge 21

[kuraakhilesh8230]

Do challenge 20 correctly and attach all the screen shots of the files which showing done and all the files should be in done only and attach that screen shot

[kuraakhilesh8230]

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

[kaushalRTJ]

Challenge 23

First find Issue - We can find the issues by using these tags [issues labeled good first issue] [issues labeled help wanted] [PRs labeled help wanted]

Comment to give confirmation of your work - Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue. Once the Issue is assigned to us, we can start our work.

Start with a clear name feature branch - A well-formed PR should start with a well-named feature branch. Developers create branches off of development for their Working on an individual feature and giving that feature branch a clear name is an important first step when collaborating with others on a single repository.

We Should give proper titles to our commits and PRs - It's a good idea to use the present imperative tense — for example, use “Added Responsive Navbar” instead of “Done”.

Descriptive PR - The more information we give to project maintainers before they look at our actual code, the easier their job will be.

Try to show functionality visually, whenever possible - Take screenshots and just paste these screenshots directly into your PR description on GitHub.

Review your own PR before you assign it to others Try to resolve any conflicts that might exist, so that merging is as easy as pressing a button. Lint our code and all DCO should be checked.

Submit PR and wait for code review and address any issues raised as soon as you can.

[kaushalRTJ]

Challenge 24

Hello star I am finding open source issue but I can't find any suitable issue. But that work in progress.

[kaushalRTJ]

Challenge 25

Finally I found HTML/CSS project and I apply in that and currently I waiting for their response.

issue link: https://github.com/imhardikdesai/Niru-Patel-Boarding-Hostel/issues/1

[kaushalRTJ]

Challenge 26

That's assign me this issue and I working on it. https://github.com/imhardikdesai/Niru-Patel-Boarding-Hostel/issues/1

Challenge 28

That is almost complete.

[kaushalRTJ]

Challenge 26

Register Complete.

[kaushalRTJ]

Challenge 27

Hectoberfest-2022

PR and MR create between 1 October to 31 October and make that public. If create spam PR/MR you got 2 chance after you will be disqualified. PR/MRs tagged with "HECTOBERFEST-ACCEPTED" if not that is "INVALID".

[kuraakhilesh8230]

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

[kaushalRTJ]

Challenge 29

https://github.com/scaleracademy/open-source-projects/discussions/114

[kaushalRTJ]

Challenge 30

I am happy with scaler effort because I haven't learn git hub. But you teach me well than other and thank you so much. I really proud.

I learn so much in scaler in last one month.

[kuraakhilesh8230]

add your own idea also in challenge-29

[kuraakhilesh8230]

Congratulations you have successfully completed milestone 4 and I hope you have had a great experience in this 30 days and learned something about this github and open source projects 🎊🎊