Day_1

[jaypansuriya104]

name: Jay Pansuriya github_user_name: jaypansuriya104

[jaypansuriya104]

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

[jaypansuriya104]

Chellenge 3

[jaypansuriya104]

Chellenge 4

[jaypansuriya104]

Chellenge 9

[jaypansuriya104]

Chellenge 11

[jaypansuriya104]

Chellenge 13

[Mrjoy832]

Good to Go 👍

[jaypansuriya104]

Chellenge 14

[jaypansuriya104]

Chellenge 16

[jaypansuriya104]

Chellenge 17

[jaypansuriya104]

Chellenge 20

[jaypansuriya104]

Chellenge 21

[kuraakhilesh8230]

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

[jaypansuriya104]

Chellenge 23

Here's are some tricks that you can learn for basic github use :+1:

Issues:

• If you're a beginner, usually begin with a good-first-difficulty tagged difficulty.
• If you need to make a few adjustments now no longer laid out in any problems otherwise you locate any bug, first create a brand new difficulty and wait till it is assigned to you.

Branch:

• Branch name should have a Group word like bug/WIP(Work in progress) .
• Try to add username in branch and make sure to not add a long descriptive name.
• Use Unique ID in branch names.
• Avoid using numbers only
• Branch with Author Name.
• Use Hyphen or Slash as Separators for easy reading.

In short, the name of these branches should match the naming convention of the rest of the team. the branch name can include words like bug, fix, WIP, the issue it will solve, author name, etc.

Pull Request

• Give your PR s descriptive title to make other easy to track your working tree.
• PR should gave some meaningful descriptions as it reduces time and complexity of your work and also decrease confusion.
• Show your functionality visually, whenever possible.

Tips:

• Give your function department a clean name
• Give your commits and PRs energetic and descriptive titles
• Streamline your system of making a brand new PR
• Give your PR a significant description
• Show your capability visually, every time possible
• Review your personal PR earlier than you assign it to others

[jaypansuriya104]

Chellenge 24

I am finding for issues that i can contribute and i find one algorithm repository that i can contribute so i make him issue for assigned me ! i am now ASSIGNED to given issue :

Issue link

[jaypansuriya104]

Chellenge 25

I have try to find solution of given issue and i find solution. After adding changes on repo. i pull request for changes. Here are link of pull request that i have made :

PR link

[jaypansuriya104]

Chellenge 26

Hectoberfest 2022

[jaypansuriya104]

Chellenge 27

• [x] Completed task of registration in Hectoberfest

Rules and regulation for Hectoberfest 2022

1. Bad repositories will be excluded
2. Any user with two or more spammy PR/MRs will be disqualified so Avoid Submitting low-quality PULL/MERGE Request.
3. 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.
4. Your PR/MRs must be made to a public, unarchived repository.
5. 4 PR created between October 1 and October 31 and PRs must be made to public, unarchived repository.
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. PR/MRs Must be merged or have an overall approving review.

[jaypansuriya104]

Chellenge 28

Update...

I make some of issue request that i can contribute and complete one contribution. Now I'm finding more issue that are suitable for me on tag with HECTOBERFEST.

I have got one more assignes on contributing on open-source-project - Notes app using html ,css ,js Here's my issue assigne link: Assigned2

[kuraakhilesh8230]

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

[jaypansuriya104]

Chellenge 29

Review

[jaypansuriya104]

Chellenge 30

• Successfully completed all the challenges of the Scaler september opensource challenge.
• By this event i have learnt a lot of things about git and github.
• make contribution , pullrequest , squash and many more are new topics to me for learning.
• Recently i have registered for the Hacktoberfest 2022, which will be my first participation in the largest opensource contributing event.
• 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.
• Thank you Scaler community for giving great and challenging challenges and for clearing all our doubts.
• Hope, there will be more open-source events like this amazing one !

[kuraakhilesh8230]

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