Day 1

[DhruvPatel033]

name: Dhruval Patel github_user_name: DhruvPatel033

[DhruvPatel033]

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

[DhruvPatel033]

Chellenge 3

[DhruvPatel033]

[DhruvPatel033]

Chellenge 9

[DhruvPatel033]

Chellenge 11

[Mrjoy832]

All Good😎😎

[DhruvPatel033]

Chellenge 13

[DhruvPatel033]

Chellenge 14

[DhruvPatel033]

Chellenge 16

[DhruvPatel033]

Chellenge 17

[DhruvPatel033]

Chellenge 20

[DhruvPatel033]

Chellenge 21

[kuraakhilesh8230]

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

[DhruvPatel033]

Chellenge 23

An overview of what I learned from reading those articles are as follows and you can read summary :

Issues: -

Always start with a "good-first-issue" tagged issue if you're a beginner. If you want to make some changes not specified in any issues or you find any bug, first create a new issue and wait until it's assigned to you.

Branches:

Git branching strategies allow separation of work. start branch name with a Group word like "bug" or "wip" based on the type of task we are working on. Use issue id in branch names - for example: jira ids if the issues are created in Jira in your work. Use Hyphen as separators to make the name easier to read, use hyphens. eg: bug-fix-submit-button instead of bugfixsubmitbutton. We can also include developer name . Don't just use issue number, it creates confusion and provides no information on why the branch was created. Don't use all naming conventions, it can make the branch name too long and very complicated to understand. Use short names for branches. These can be categorized into Regular Branching and Temporary Branching.

PR :

Give your PR a meaningful description Before making a pull request, review the modifications. Try to include screenshots of the things you added in action.

[DhruvPatel033]

Chellenge 24

I am finding issues for solving and making solutions of it and find out issue that i can contribute into. I make him request for contribution on it. AND i am accepted. I am ASSIGNED for given issue :

Assigned issue link

[DhruvPatel033]

Chellenge 25

I have forked repo of assigned issue and work on it to make some change. I do make form the HTML and CSS in file and further it will be more effective and responsive. here's my PR link that i have made :

Pull Request

[DhruvPatel033]

Chellenge 26

I successfully registered in Hectoberfest 2022

[DhruvPatel033]

Chellenge 27

Completed registration process in prevoius chellenge.

Tips for Hectoberfest 2022

1. PR/MRs must be created between October 1 and October 31 and PRs must be made to public, unarchived repository.
2. PR/MRs that their system detects as spammy will also not be counted.
3. spammy pull/merge requests will be labeled as “spam.”
4. PR/MRs must be tagged “HACKTOBERFEST” or must be labeled “HACKTOBERFEST-ACCEPTED".
5. Maintainers accept PR/MRs by merging them, labeling them “hacktoberfest-accepted,” or giving them an overall approving review. Accepted PR/MRs enter a 7-day review window, during which approval can be revoked by the maintainer or by our team.
6. PR/MRs should be useful to maintainers. Repos that encourage simplistic PR/MRs (like adding a name or profile to a list or arbitrarily curating content) will be excluded from Hacktoberfest. Remember: quantity is fun, quality is key.
7. Avoid Submitting low-quality PULL/MERGE Request.

[DhruvPatel033]

Chellenge 28

UPDATE !

Working on previous assigned project and waiting for approval of pull request. pull_request_1

Trying to search issues for contribution with special tag of Hectoberfest.

I have try to find some intermideate projects for make contribution that suits me and i find one more project that i can make better and waiting for assign. issue_2

[DhruvPatel033]

Chellenge 29

review

[DhruvPatel033]

Chellenge 30

• Finally completed all the challenges of the Scaler september opensource challenge.
• By this event i have learnt a lot of things about git and github.
• By doing all these challenges i have got a knowledge about git and github.
• I am very thankful for Scaler academy for organizing this type of events which helps many of the people to learn a lot of things.
• Recently i have registered for the Hacktoberfest 2022, which will be my first participation in the largest opensource contributing event.
• Thank you Scaler community for giving great and challenging challenges and for clearing all our doubts.
• Thank You Scaler Academy.
• Hope, there will be more open-source events like this amazing one !

[kuraakhilesh8230]

congrats you have successfully completed milestone 4 😎