Challenges 30/30 - kobruhhhhh

[kobruhhhhh]

name: Lalit Kumar github_user_name: kobruhhhhh

[kobruhhhhh]

URL - https://github.com/kobruhhhhh/scaler-september-open-source-challenge Screenshot -

[kobruhhhhh]

Challenge - 3 Screenshot of all the current branches inside my forked cloned repository :

[kobruhhhhh]

Challenge - 4 Screenshot showing the latest repository contents.

[kobruhhhhh]

Challenge - 9

[kobruhhhhh]

Challenge -11

[kobruhhhhh]

Challenge - 13

[kobruhhhhh]

Challenge - 14

[kobruhhhhh]

Challenge -15

changes reflected in the PR

[kobruhhhhh]

Challenge - 16

No conflicts in the PR

[kobruhhhhh]

Challenge - 17

The demo repo - scaler-github-desktop

Downloaded Github Desktop and Created New Repo and Pushed it to Github:

Created new branch kobruhhhhh-demo:

Made changes to README.md in the demo branch:

Commited and Pushed changes via demo branch and raised a PR to the main branch:

Merged the PR and Pulled from the origin into the kobruhhhhh-demo branch:

[kobruhhhhh]

Challenge - 20

Repo

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

[kobruhhhhh]

Challenge - 21

Creating and Using Alias

[kobruhhhhh]

Challenge - 23

What must be done to effectively contribute to open source

Issues: -

• Always start with a "good-first-issue" tagged issue if you're a beginner.
• If you want to make some changes not specified in any issues or you find any bug, first create a new issue and wait until it's assigned to you.

Branches: -

Git branching strategies allow separation of work.

• start branch name with a Group word like "bug" or "wip" based on the type of task we are working on
• use issue id in branch names - for example: jira ids if the issues are created in Jira in your work
• Use Hyphen as separators to make the name easier to read, use hyphens. eg: bug-fix-submit-button instead of bugfixsubmitbutton
• we can also include developer name . eg:
• Don't just use issue number, it creates confusion and provides no information on why the branch was created
• Don't use all naming conventions, 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 doesn't 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 master
• 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. Some examples:

• Bug Fix - Created to fix a bug
• Hot Fix
• Feature Branches
• Experimental Branches
• WIP branches - Work in Progress branches

Pull Request: -

1 -The pull request created should be descriptive of the problem that is being solved. 2 -It should refer to the issue which the pull request closes. 3 -The pull request should be created from a feature branch of the forked repo and not the main. 4 -The changes should be reviewed and tested before creating pull request.

Tips: -

• Give your feature branch a clear name
• Give your commits and PRs active and descriptive titles
• Give your PR a meaningful description
• Show your functionality visually, whenever possible
• Review your own PR before you assign it to others

[kobruhhhhh]

Challenge - 24

I have been assigned to 2 issue

• https://github.com/techysubham/Communitea-Discord-Bot/issues/5
• https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/issues/27

[kobruhhhhh]

Challenge - 25

Found a Beginners Project and created a Pull Request

Add Lalit Kumar

[kobruhhhhh]

Challenge - 26

Registered for Hacktoberfest 2022 as Contributor

[Mrjoy832]

Milestone-3 Done

[kobruhhhhh]

Challenge - 27

Tips for contributing to Hacktoberfest

• Follow Hacktoberfest rules.
• Start looking for issues early. Likewise, start working early on assigned issues instead of postponing it to next day.
• Look for issues with label good-first-issue, beginner for beginner-friendly tasks.
• Only PRs in repos that are participating in Hacktoberfest will get counted towards progress. So, check if a repo is a participating repo.
• Read contributing guidelines of repo and write quality code with a consistent style.
• Do not spam comments on issues or make spammy PRs.
• The PR should be made to public, unarchived repository.
• Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest

[kobruhhhhh]

Challenge - 28

I've been assigned 2 issues in last 3 days.

1 of my PR approved and merged successfully in the site.

• https://github.com/Syknapse/Contribute-To-This-Project/pull/1679

  

• Changes appeared on the project's website Link to website

Looking for more issues to contribute to in Hacktoberfest.

[kobruhhhhh]

Challenge - 29

• https://github.com/scaleracademy/open-source-projects/discussions/96
• https://github.com/scaleracademy/open-source-projects/discussions/63

Screenshots showing upvotes

Screenshot of idea created in a discussion

• https://github.com/scaleracademy/open-source-projects/discussions/147

[kobruhhhhh]

Challenge 30

Successfully completed all the challenges. Through this challenge, I knew about how to contribute, make a repository, make PR, and create issues as well as how to use git bash or GitHub. Thanks to Scaler for organizing it, everyone in the community was helpful and encouraged a lot during these 30 days. If tried alone it would have taken more than 30 days for sure but with the help of these challenges and help from others, learning was exponential. I will continue my journey of open source, really excited about Hactoberfest as this will be the first time I will participate.

[Mrjoy832]

Milestone-4 done ✅