Challenge-1 to 30

[rahul09999]

name: Rahul lalwani github_user_name: rahul09999

[rahul09999]

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

[rahul09999]

[rahul09999]

[rahul09999]

challenge-9

[rahul09999]

Created another branch from current branch-Challenge 11

[rahul09999]

Challenge 13- Git Stash and delete that changes

[DaltonDeven]

✅ Good to go verified

[rahul09999]

challenge-14 I by mistake didnt delete conflicters(<<<<<<<,=======,>>>>>>),but then i reset and done merge again and done what the challenge asked for:-

[rahul09999]

Challenge 16:-

[rahul09999]

Challenge-17

[rahul09999]

Challenge - 18

[rahul09999]

Challenge-20

Created project board-

Added cards in Todo column-

Moved cards from Todo to progress column

Moved the card from In progress column to Done column

Remaining card moved from Todo to in progress

All issues solved so cards moved to done

[rahul09999]

Challenge-21

Making and List of alias

Usage of alias

[kuraakhilesh8230]

Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best✅️

[rahul09999]

Challenge 23

Things I understood and found important after going through the resources provided by you:

For issue:

1. 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.
2. new issue created should have clear purpose.
3. Scan through existing issues to find one that interests you. search can be narrowed using labels as filters like easy difficulty task, question ,etc.
4. Comment on it and say you're working on that issue. to avoid conflicts with others also working on the issue.

For branch creation:

1. branch are mostly of two types Regular(permanent bases) & Temporary Branches(fixing or new feature).
2. branch name should have a Group word like bug/WIP.
3. Unique IDs in branch names.
4. Use Hyphen or Slash as Separators for easy reading.
5. Branch with Author Name.
6. Avoid long descriptive names for branches.

For pull request:

1. Give your commits and PRs descriptive titles.
2. meaningful description.
3. Show your functionality visually, whenever possible like adding screenshots.
4. link PR to issue if you are solving one.

[rahul09999]

Challenge-24

Day-1

Research various repo from beginner friendly to good first issues, but still not found any suitable issues which can be done with my basic knowledge. As of now i might start exploring out with https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems and trying to figure out how can i contribute in that as my first official real contribution in Github world.

Day-2(challenge-25)

Asked here to assign me this issue for README.md file contribution Raised a new issue and It got assigned to me, you can check here Also I raised pull request for above mentioned issue after solving it, you can find it here

Day-3(Challenge-26)

Today I learned about what hacktoberfest exactly is through various videos/articles and I am going to register in that for sure. Update, I registered in hacktoberfest-

Also I'll work on issue which was assigned to me previous, as it is bit of tedious task so it might take few days until it finally got merged. I'll try to update tomorrow about the progression for same.

Day-4(Challenge-27)

I registered for hacktoberfest previous night only, ss is provided above.

Tips for hacktoberfest-

1.The Opensource contributions are not only about coding, enhancements, and bug fixes. It is way more than that. -You can contribute to a project's documentation, automation, build, test, and many more. 2.Make meaningful contributions, please don't spam unnecessarily in issue and pull request. 3.You need minimum 4 contribution for hacktoberfest, but not limit yourself to only 4 contribution.

4. Event like Hacktoberfest is an excellent opportunity for the tech communities to come together, build networking, make friends for a lifetime.
5. You can start looking here for all the projects taking part in the hacktoberfest by clicking below.

Hacktoberfest repositories

Day-4(Challenge-28)

1. Yes, I have contributed in some issues which are suitable for first time contributors. Below I am attaching some link of my issue/PR's -- First time contributions' PR -- Added one solution of function problem of cpp lang -- Currently assigned issue, it might take sometime to complete it
2. As I am a beginner I need to learn few tech stacks first to start doing open source contributions frequently, until then I'll try to find some easy or documentation related issues and contribute for same

Day-5(Challenge-29)

I really liked below project ideas:- Also today I got to know, there I specific discussion section in Github

Day-6(Challenge-30)

APPRECIATION NOTE

First of all really thanks to scaler and team to organize such a good challenge while I was planning to learn git but you bcz of know procrastination I always can't able to start but due to this challenge I can able to learn each topic/day and gather a lot of information's -Secondly again thx to admins to build a great discord community, this community helps me every time whenever I stuck with anything during challenge. Ps-special thx to deepanshu bhaiya and christus bhaiya from discord. -Lastly thx to @shivaylamba for building this challenge is structuralized format, only bcz of that we can learn all the beginners topics (best part was toughness of challenges are increasing gradually) -Last note, I wish that scaler and team should creates such type of challenges more frequently in near future

Thx to all admins, scaler stars, mods, discord community, shivay and scaler from my ❤️

[DaltonDeven]

All Set To Go Verified for Milestone-3 Congrats👍

[kuraakhilesh8230]

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