Challenge - 1 - 30

[srinjoy-26]

name: Srinjoy Pati github_user_name: srinjoy-26

[srinjoy-26]

challenge - 2 https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/474

[srinjoy-26]

challenge - 3

[srinjoy-26]

challenge - 4

[srinjoy-26]

link of PR - https://github.com/scaleracademy/scaler-september-open-source-challenge/pull/796

[srinjoy-26]

Challenge 9

removed all commits of challenge 8

[srinjoy-26]

challenge 10

passed all DCO checks

[srinjoy-26]

Challenge 11

[srinjoy-26]

challenge 13

using git stash

[kuraakhilesh8230]

challenge - 2 #474

send ss of this challenge

[srinjoy-26]

challenge - 2 #474

send ss of this challenge

[srinjoy-26]

challenge 14

[kuraakhilesh8230]

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

[srinjoy-26]

challenge 16

[srinjoy-26]

challenge 17

repo link - https://github.com/srinjoy-26/desktop-tutorial

[srinjoy-26]

Challenge 18

[srinjoy-26]

challenge 19

all linter checks passed

[srinjoy-26]

challenge 20

link to repo : https://github.com/srinjoy-26/Hotel-finder link to board : https://github.com/users/srinjoy-26/projects/1/views/1

[srinjoy-26]

challenge 21

[kuraakhilesh8230]

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

[srinjoy-26]

Challenge 23

While contributing to Open Source, we must try to follow some of the best practices for effective contribution, especially with respect to open source issue creation, best practices around branch/pull request creation.

What must be done to effectively contribute to open source?

Issues:

• Always start with a good-first-issue tagged issue, in case you are a beginner.

• If you want to make changes which are not specified in any issue, or you find any bug, first create a new issue and then wait until it is assigned to you.

  Branches:

  Git branching strategies allow separation of work.

• Start the branch name with a group word like "bug" or "wip" based on the type of task you are working on.

• Use Issue ID in branch names.

• To make the name easier to read, use a hyphen as a separator. eg: use bug-fix-submit-button, instead of bugfixsubmitbutton.

• Do not use all the naming conventions as 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'.

Regular Branching

• master branch: It is the default branch of GIT and this branch does not allow direct check-ins. Code should be merged with master after code review ONLY.

• dev branch : This is mainly used by developers to make any new changes in the code. Once the changes have been made, testing is performed on this branch and then after the final code review, a pull request is created to the Master branch and the changes are merged with it.

• QA or test branch: It contains code for QA testing and automation testing of all changes implemented. Before any change goes to the production, it must undergo QA testing to get a stable codebase.

  Temporary Git Branches

  These are branches that can be created and deleted after the task is complete. Example:

• Bug Fix - created to fix a bug

• Hot Fix

• Feature branches

• Experimental branches

• WIP branches - Work in Progress branches

Pull Request:

• your commits and PRs must have descriptive titles.
• They should have meaningful description.
• The pull request should be created from a feature branch of the forked repo and not the main.
• The changes should be reviewed and tested before creating pull request.

[srinjoy-26]

challenge 24

Progress

• I have found an open source repository based on web and python.
• I have opened a new issue, and have commented the owner to assign me.

[srinjoy-26]

challenge 25

• One of my issues got assigned to me and I have started working on it.
• Issue link - https://github.com/Sulagna-Dutta-Roy/Webeginner-projects/issues/311
• will create a Pull request soon and will update the progress here.
• My PR -> https://github.com/Sulagna-Dutta-Roy/Webeginner-projects/pull/315

[srinjoy-26]

challenge 26

• Registered for hacktober fest 22

• badge https://www.linkedin.com/posts/srinjoy-pati-7b14301b7_i-got-the-hacktoberfest-2022-registered-activity-6980226449265831936-AlY5?utm_source=share&utm_medium=member_android

[srinjoy-26]

challenge 27

Tips :

• Make sure the PR should not be spam or low quality.
• The PR must be in a repo tagged with the "HACKOCTOBERFEST" topic, or be labelled "HACKOCTOBERFEST-ACCEPTED".
• In order to be eligible for the t-shirt you must be in the top 40000 people to achieve 4 successful and quality PR merges.
• The PR must be created between Oct 01 - Oct 31.
• The PR should be made to public, unarchived repository.
• Read contributing guidelines of repo and write quality code with consistent style.

[srinjoy-26]

challenge 28

After creating the last PR , mentors of that repo are still reviewing my changes and I'm getting Positive responses .They even requested changes which I have done . Now for hacktober fest I have got some repos to contribute and currently I have been assigned an issue in one of the repo, for which I will be creating a PR soon. -https://github.com/fineanmol/Hacktoberfest2022/issues/1353#event-7483027618

[srinjoy-26]

challenge 29

I liked and upvoted this idea.

[srinjoy-26]

challenge 30

• I hv completed all the challenges .
• So since its ending , I would like to thank scaler , @shivaylamba , @kuraakhilesh8230 and everyone for such an amazing event. I got to learn several things regarding opensource , git , github , github desktop , VS code . Thanks.
• one of my PR got merged today , its very exciting.

[kuraakhilesh8230]

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