September-Challenge: Sourav Chandra Dey

[scd-02]

name: Sourav Chandra Dey github_user_name: scd-02 discord_id: scd_02

[scd-02]

#Day 2

URL: https://github.com/scd-02/scaler-open-source-september-challenge.git

[scd-02]

#Day3

[scd-02]

#Day 4

main branch:-

scd-02-details branch:-

[scd-02]

#Day5

[scd-02]

#Day 6

[scd-02]

#Day 7

[scd-02]

#Day 8

[scd-02]

#Day 9

[scd-02]

#Day 10

[scd-02]

#Day 11

[scd-02]

#Day 12

[scd-02]

#Day 13

About VScode About Java snippet

[scd-02]

#Day 14

[scd-02]

#Day 15

[scd-02]

#Day 16

[scd-02]

#Day 17

[scd-02]

#Day 18

[scd-02]

#Day 19

It was fun using github codespace. I can have access to my projects from anywhere and I don't need to carry laptop. I can also explore collab and different language all over in one place. I can also work in collaboration with my teammates for hackathon and different projects. Yeah I love it!

[scd-02]

#Day 20

[scd-02]

#Day 21

[scd-02]

#Day 22

[scd-02]

#Day 23

[scd-02]

#Day 24

Git Branches

We can divide Git branches into:

1. Regular Branches: Permanent branches in the repository
2. Dev: Used for making changes in the code
3. QA: Used for all automation testing

Master: Default Branch

Temporary Branches: To be deleted when needed

• Bug fix
• Hot fix
• Feature Branch
• Experimental Branch
• WIP(Work in progress) branch

Conventions:

• Start branch name with group words like WIP, feature, etc.
• Use unique ID in names if there are any, like bug ID.
• Use a hyphen or slash as a separator between words for better readability.
• Use the author's name for the branch so that the organization evaluator can know who is the owner of the branch.
• Avoid long names for permanent branches.
• Avoid using every convention together.

Building a great PR

• Well-named feature branch.
• Write appropriate commit messages and PR descriptions.
• Give meaningful PR descriptions by describing "WHY?", "HOW?" and "WHAT?".
• Add visual representation whenever possible for a better understanding.
• Review the PR, update the latest changes, merge any pull request, and then assign it to others.

Contributing Code

• A beginner should start with a 'good-first-issue' tag.
• Look for issues with the tag 'help wanted' or 'good first issue', these issues are meant for community contributions.
• Issues with tags ' status: blocked', ' status: awaiting triage', and 'status: ticket work required' are also not ready for the community.
• Issues with the tag 'staff only' are not meant for the community.

Contribution Process:

1. Choose the issue to work on, and do the following:
2. Comment on the issue.
3. Add the features make changes that are needed and submit PR, following all the PR guidelines.
4. Wait for feedback and collaborate accordingly.

Proposing a new Issue: Cannot find an issue to work on, create a new issue on the relevant repository including details about the implementation, and wait for feedback.

[scd-02]

#Day 25

I am still looking for the good first issue to contribute to the open source.

[scd-02]

#Day 26

Continuation of challenge 25 I am still searching for open-source projects to which I can contribute.

[scd-02]

#Day 27

Link to repo

[scd-02]

#Day 28 Registered for Hacktoberfest and hackathon and still searching for a repo to contribute.

[scd-02]

#Day 29

Profile Link

[scd-02]

#Day 30

I have completed all the tasks and I am searching for an open source repo to contribute. Booyah!