Challenge 1-30

[gauriimaheshwarii]

name: Gauri Maheshwari github_user_name: gauriimaheshwarii

[gauriimaheshwarii]

URL of forked repository: https://github.com/gauriimaheshwarii/scaler-september-open-source-challenge

[gauriimaheshwarii]

[gauriimaheshwarii]

Challenge 4: Screenshot showing the latest repository contents

[gauriimaheshwarii]

Challenge 9

[gauriimaheshwarii]

Challenge 10

[gauriimaheshwarii]

Challenge 11

[gauriimaheshwarii]

Challenge 12: Squash the commits in pull request with sign

[gauriimaheshwarii]

Challenge 13

[gauriimaheshwarii]

Challenge 14

[gauriimaheshwarii]

Challenge 15

[gauriimaheshwarii]

Challenge 16: Fixed merge conflict

[gauriimaheshwarii]

Challenge 17

Downloaded GitHub Desktop and created new repository scaler-github-gauri-maheshwari and pushed it to GitHub:

Created new branch gauri-demo:

Made changes to README.md in the gauri-demo branch:

Committed and pushed changes via gauri-demo branch and raised a PR to the main branch:

Merged the PR and pulled from the origin into the gauri-demo branch:

GitHub repository after task completion:

[gauriimaheshwarii]

Challenge 18

Gist 1:

Gist 2:

[gauriimaheshwarii]

Challenge 20

Repository Project Board

Created a GitHub repository

Created a Project Board with a TODO, In Progress and Done columns

Completed the In Progress task and moved the card to the Done column

[gauriimaheshwarii]

Challenge 21

Creating and Using Alias

[gauriimaheshwarii]

Challenge 22

Repository

Website

[DaltonDeven]

All set to go verified for Milestone-2👍

[gauriimaheshwarii]

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:

• The pull request created should be descriptive of the problem that is being solved.
• It should refer to the issue which the pull request closes.
• 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.

Extras:

• GitHub is a great tool to interact and collaborate with others. Be social, and try to explore new things and learn from the GitHub Community.
• While contributing in any repository, make sure you check the guidelines laid by its owner in CONTRIBUTING.md, and raise PRs following the rules.
• PRs have multiple features and functionalities. Make sure to read about the essential things to know about PRs listed at All About PRs.

[gauriimaheshwarii]

Challenge 24

Search for good-first-issues to make contributions.

Status:

Searched for issues to contribute to. My tech stacks include C++, Python. and Flutter. Explored quite some issues, but felt that most of the issues were beyond my contributing knowledge. Will update as soon as I find an issue to contribute to.

[gauriimaheshwarii]

Challenge 25

Got assigned this issue.

• https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/issues/107

Asked for this issue to be assigned to me.

• https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/issues/142

[gauriimaheshwarii]

Challenge 26

(updates on Challenge 25)

• Made the Pull Request for the assigned issue and got a merge approval. https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/issues/107

[gauriimaheshwarii]

Challenge 26

Registered for Hacktoberfest.

[gauriimaheshwarii]

Challenge 27

What you need to know to participate and complete Hacktoberfest:

• Register anytime between September 26 and October 31.
• Pull requests can be made in any GITHUB or GITLAB hosted project that’s participating in Hacktoberfest (look for the “hacktoberfest” topic).
• Project maintainers must accept your pull/merge requests for them to count toward your total.
• Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest.
• The first 40,000 participants (maintainers and contributors) who complete Hacktoberfest can elect to receive one of two prizes: a tree planted in their name, or the Hacktoberfest 2022 T-shirt.

Some tips for Hacktoberfest 2022:

• The PR/MR's must be within the bounds of Hacktoberfest.
• Repositories that go against Hacktoberfest's values will be excluded from qualification and PR/MR's made to those repositories will not count.
• The PR/MR's must not be spammy.
• The PR/MR's must be in a repository tagged with the "Hacktoberfest" topic, or be labeled "Hacktoberfest-accepted".
• The PR/MR's must not be labeled as "Invalid".
• The PR/MR's must be merged, having the "Hacktoberfest-accepted" label, or have an overall approving review.

Resources for beginners:

Introduction to open-source:

• DigitalOcean: Introduction to GitHub and open-source projects
• GitHub: How to contribute to open-source
• DigitalOcean: What is open-source
• DigitalOcean: How to use Git

Start contributing:

• List of beginner repositories: UP-FOR-GRABS.NET
• GitHub repository: FIRST-CONTRIBUTIONS
• GitHub repository: AWESOME-FOR-BEGINNERS

[gauriimaheshwarii]

Challenge 28

• Got my PR merged for the issue created.

• Looking for more open-source projects to work on and contribute to.

[gauriimaheshwarii]

Challenge 29

• Found this idea quite interesting and would like to work on it.

[gauriimaheshwarii]

Challenge 30

Successfully completed all the challenges. Through this challenge, I learnt to contribute, make a repository, make PR, create issues and use Git Bash or GitHub. Thank you Scaler for organizing it, everyone in the community was helpful and encouraged a lot during these 30 days.

I will continue my journey of open source and am really excited about Hactoberfest as this will be the first time I will participate.

[Mrjoy832]

Milestone-4 done ✅