Scaler Open Source Challenges

[kishanrajput23]

Challenge 1

• name : Kishan Kumar Rai
• github_user_name : kishanrajput23

[kishanrajput23]

Challenge 2

• URL of my forked repository : https://github.com/kishanrajput23/scaler-september-open-source-challenge/tree/main

• A screenshot of the cloned project in my system

[kishanrajput23]

Challenge 3

• Screenshot showing the list of all the current branches inside my forked clone repository

[kishanrajput23]

Challenge 4

• Screenshot showing the latest repository contents

[kishanrajput23]

Challenge 9

• Identify the commit id that needs to be removed (you should have created this in the 8th Challenge)
• Use git reset and force push, to remove the commit from your pull request.
• Share a screenshot of this, in the issue you created in previous challenges.

[kishanrajput23]

Challenge 11

• Git Commands

• Repository View

[kishanrajput23]

Challenge 13

• Use the git stash command to move these changes to the stash area.
• Delete the content from the stash area and share a screenshot of this inside the GitHub issue created in the first challenge.

[kishanrajput23]

Challenge 14

• Created a scenario of a merge conflict locally in my system for a project that I can create.

[kishanrajput23]

Challenge 16

• Resolved conflicts

[kishanrajput23]

Challenge 17

• Downloaded GitHub Desktop

• Created a Repository

• Added & Edited the file

• Commit New File

• Publish A Repository

• Publish New Branch & Created New Pull Request

• Repository Link : Visit Here

[kishanrajput23]

Challenge 20

• Repository Link : VISIT HERE

• Project Link : VISIT HERE

[kishanrajput23]

Challenge 21

[kuraakhilesh8230]

Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best ✅️

[kishanrajput23]

Challenge 23

Here are the summary which I learnt from today's task.

📌Git Branching Naming Convention : Best Practices

Git branches are of two types:

1. Regular
2. Temporary Branches

🔸Regular Branches

• These branches will be available in your repository on permanent bases.
• Their naming convention is simple and straightforward.

🔸Temporary Git Branches

As the name indicates, these are the branches that can be created and deleted when needed. They can be as follows:

• Bug Fix
• Hot Fix
• Feature Branches
• Experimental Branches
• WIP branches

📌Git Branching Naming Convention

1. Start branch name with a Group word like Bug – The bug which needs to be fixed soon
2. Use Unique ID in branch names like wip-8712-add-testing-module
3. Use Hyphen or Slash as Separators like feature_upgrade_jquery_version_login_module
4. Git Branch with Author Name like <author>_<branch-type>_<branch-name>
5. Avoid using numbers only like 9912
6. Avoid using all naming convention simultaneously
7. Avoid long descriptive names for long-lived branches like wip_login_module_which_will_used_in_the_public_website

📌Building a Great Pull Request

1. Give your feature branch a clear name
2. Give your commits and PRs active and descriptive titles
3. Streamline your process of creating a new PR
4. Give your PR a meaningful description
5. Show your functionality visually, whenever possible

📌Contributing Guidelines

1. Always see for good-first-issue in the repos.
2. Comment on it and say you're working on that issue, to avoid conflicts with others while also working on the issue.
3. 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.
4. Have a clear purpose while creating a new issue.
5. Avoid long descriptive names

🙍‍♂️Author : @kishanrajput23

[kishanrajput23]

Challenge 24

Finally after a lot of research I found an issue that is suitable for me and also got an approval to work on that.

• https://github.com/Ashutosh00710/github-readme-activity-graph/issues/25

Looking forward to do some awesome contribution.

Challenge 25

Started working on issue on which I assigned yesterday. Created a new open source project for helping beginners like me to get started with open source.

• Hacktoberfest-2022

Challenge 26

• Registered for Hacktoberfest 2022

• Worked on my Open Source Project so that I can help other folks to get started with Open Source.

[kishanrajput23]

Challenge 27

Contributors Guidelines

• 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.

• Project maintainers must accept your pull/merge requests for them to count toward our total.

• Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest.

• Only 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.

Resources For Beginners

Intro 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

  Worked on my Open Source Project , created new issues, review others code and accepted few PR's.

[kishanrajput23]

Challenge 28

Pull Requests

• https://github.com/Rjndrkha/HacktoberFest_2022/pull/287

• https://github.com/OtacilioN/awesome-hacktoberfest-2022/pull/453

• https://github.com/fineanmol/Hacktoberfest2022/pull/1350

My Project

• https://github.com/kishanrajput23/Hacktoberfest-2022

[kishanrajput23]

Challenge 29

Upvoted Ideas

• https://github.com/scaleracademy/open-source-projects/discussions/63#discussioncomment-3765698
• https://github.com/scaleracademy/open-source-projects/discussions/45#discussioncomment-3765728

Screenshots For Proof

My Idea

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

[kishanrajput23]

Challenge 30

So, finally this 30 days of open source event came to an end and really throughout this whole event I learnt a lot of new things in Git & GitHub. There was some days when I thought I should just give up and leave this challenge because some of the task were really frustrating me. But, by the time I learnt that concepts and I was to able to complete the challenges. At last I'd like to thank whole discord community because without them I was unable to complete those challenges. A special thanks to @shivaylamba for making us 1℅ better everyday by providing different challenges on each day. Also I'm grateful to @kuraakhilesh8230 for his help and support.

Thank You Again!!

[Mrjoy832]

Milestone-4 done ✅