Challenge #1-Ayan Bhunia

[ayanbhunia2002]

name: Ayan Bhunia github_user_name: ayanbhunia2002 discord_id: 806046660231823400

[ayanbhunia2002]

URL of my forked repository

Screenshot of the cloned repo :

[ayanbhunia2002]

Creation of a new branch locally in my forked clone repository

[ayanbhunia2002]

Task - 4

[ayanbhunia2002]

Task - 7

[ayanbhunia2002]

Task - 8

[ayanbhunia2002]

Task - 9

[ayanbhunia2002]

Task - 10

[ayanbhunia2002]

Task - 11

[ayanbhunia2002]

Task - 12

[ayanbhunia2002]

Task : 13

[ayanbhunia2002]

Task - 14

[ayanbhunia2002]

Task - 15

[ayanbhunia2002]

Task - 16 completed

[ayanbhunia2002]

Task - 17

[ayanbhunia2002]

Task - 18

branches in GitHub desktop:

commit the changes :

pulling :

pushing :

History :

Github remote :

[ayanbhunia2002]

Task - 19

[ayanbhunia2002]

Task - 20

[ayanbhunia2002]

Task - 21

[ayanbhunia2002]

Task - 22

[ayanbhunia2002]

Task - 23

[ayanbhunia2002]

Task - 24

Git Branching : Git branching strategies allow the separation of work. Broadly, we can divide Git branches into two categories: Regular and temporary Branches.

Regular Branches Dev: Developers push changes into this branch. Master: No one should directly push their code into the Master branch. After code review, one branch should be merged into the master branch. QA: r test branch, contains all the code for QA testing and automation testing of all changes implemented

Temp Branches

Bug Fix Hot Fix Feature Branches Experimental Branches WIP branches

Naming Convention :

• Start with group word that match workflow.
• Use Unique ID in branch names
• Use Hyphen or Slash as Separators
• Git Branch with Author Name
• Avoid using numbers only

Pull Request creation :

• If your project has more than two contributors, it can be useful to prefix your branch names with your initials

• Also, if you've created a PR that's not quite ready to be merged, give the title a prefix like “WIP:” or “IN PROGRESS:” to avoid someone accidentally reviewing your work prematurely.

• Give your PR a meaningful description

• A PR description section is where you let the reviewer know why you opened the pull request; the more information you give them before they look at your actual code, the easier their job will be. A basic description usually has these elements:

"Why?" Why is this new code necessary? Providing a little extra context helps give your reviewer a clearer understanding of what they are about to be looking at. "How?" Provide a bullet point list of the most important commits, expanding on each as necessary. "What?" Demonstrate the functionality that was added or changed, calling out particular parts of your feature that warrant extra attention. Images and animated GIFs are a great way to do this.

• Show your functionality visually, whenever possible

Issue finding and creation : Issues available for community contribution: The following tags mark issues that are open for community contribution:

• help wanted: Open to participation from the community but not necessarily beginner-friendly
• good first issue: Open to participation from the community and friendly towards new contributors

[ayanbhunia2002]

Task - 25

As per the task, I have explored a lot of open-source projects but couldn't able to find a project where I could contribute as per my Tech stack. Hopefully, by tomorrow I will be able to find a project for contribution.

[ayanbhunia2002]

Challenge - 26

I have registered for Scaler OpenQuest Hackathon.

I have found a project where I can contribute. I have forked that repository and cloned it to my local machine and now I'm actively engaged in the process of getting acquainted with the codebase.

[ayanbhunia2002]

Challenge - 27

[ayanbhunia2002]

Challenge - 28

Challenge 25 progress : I have made one pull request Repo link : https://github.com/sukriti-kuila/Birthday-wish-generator/pull/3/commits

I have for registered For Hacktoberfest :

[ayanbhunia2002]

Challenge - 29

My github profile readme :

[ayanbhunia2002]

Challenge - 30

filled up the form - Milestone 4 :

My Experience : This challenge was too awesome. I have learnt a lot of essential concepts. I think it is a wonderful experience.