Challenges(upto 30)

[RidhikaJoshi]

name: Ridhika Joshi github_user_name: RidhikaJoshi

[RidhikaJoshi]

https://github.com/RidhikaJoshi/scaler-september-open-source-challenge

[RidhikaJoshi]

[RidhikaJoshi]

[RidhikaJoshi]

[RidhikaJoshi]

https://github.com/scaleracademy/scaler-september-open-source-challenge/pull/718/commits

[RidhikaJoshi]

Before reset

After reset

[RidhikaJoshi]

Challenge 10

[RidhikaJoshi]

Challenge-11

[RidhikaJoshi]

Challenge 12

[RidhikaJoshi]

Challenge-13

[RidhikaJoshi]

Challenge -14

[RidhikaJoshi]

Challenge -15

[RidhikaJoshi]

Challenge-16: Fixed Merge Conflict. Before:

After:

[RidhikaJoshi]

Challenge -17

Installed GitHub Desktop and Created Challenge-17 Repository

Adding Commits

Pushing Changes to GitHub Repository

Repo Link- https://github.com/RidhikaJoshi/Challenge-17

Creating New Branch(Test-Branch)

Publishing New Branch to the GitHub

Commiting Changes in new branch(Test-Branch)

[RidhikaJoshi]

Challenge-18

[RidhikaJoshi]

Challenge-19

Fixed Lint Errors

[RidhikaJoshi]

Challenge-20

Created a GitHub Repository

Repo Link- https://github.com/RidhikaJoshi/Algorithms-Project

Created a project board with a TODO column, In progress, Done and Created a card for all the items in the TODO column

[RidhikaJoshi]

Challenge-21

I've gone through the Git Alias documentation. Created 4 alias for git commands(checkout, branch, commit and status) Screenshot of the alias I've created.

[kuraakhilesh8230]

Do challenge 20 correctly and attach screen shots of all the files of your project which should show done after moving from inprogress

[RidhikaJoshi]

Challenge-22

Created Repository- https://github.com/RidhikaJoshi/RidhikaJoshi.github.io

Uploaded On GitHub Pages - https://ridhikajoshi.github.io/

[RidhikaJoshi]

Challenge-23

Git Branches

Branch Categories

• Regular Git Branches: Development (dev), Master (master) and QA (QA)
• Temporary Git Branches: Bug Fix, Hot Fix, Feature Branches, Experimental Branches and WIP branches.

Git Branching Naming Convention

• Start branch name with a Group word.
• Use Unique ID in branch names.
• Use Hyphen or Slash as Separators.
• Git Branch with Author Name.
• Avoid using numbers only.
• Avoid using all naming convention simultaneously.
• Avoid long descriptive names for long-lived branches.

Pull Request

Useful Tips

• Give your feature branch a clear name.

  A well-formed PR should start with a well-named feature branch.

• Give your commits and PRs active and descriptive titles.

  For both commit messages and PR titles, it's a good idea to use the present imperative tense — for example, use “Fix dashboard typo” instead of “Fixed” or “Fixes.”

• Streamline your process of creating a new PR.

• 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 How and What

• Show your functionality visually, whenever possible

• Review your own PR before you assign it to others

  • Make sure you are caught up with the latest changes in the develop branch; resolve any conflicts that might exist, so that merging is as easy as pressing a button.
  • Run your tests!
  • Lint your code!

Contributing Guidlines

Finding an Issue to Work On:-

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

• Issues not available for community contribution:

  🔒 staff only: Requires infrastructure access or institutional knowledge that would be impractical to provide to the community.

• Issues not ready for work:

  🚧 status: blocked: Blocked by other work that needs to be done first 🧹 status: ticket work required: Needs additional work before it is ready to be taken up 🚦 status: awaiting triage: Has not been triaged by a maintainer.

• Issues without any of the above labels.

Contribution Process

• Identify issue to work on basis on above guidelines, and comment on it to avoid conflicts.
• Write code and submit PR. PR should follow guidleines.
• Wait for code review and address any issues raised as soon as you can.

Submitting a New Issue

• Create a new GitHub issue associated with the relevant repository and propose your change there.
• Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.
• Once the project maintainer has approved the issue (by removing the 🚦 status: awaiting triage label), start work on code as described in above section.

[RidhikaJoshi]

Challenge-24

Found an issue which is related to my technical skills and I have commented on it if I can contribute:

https://github.com/OpenGenus/cosmos/issues/6341#issuecomment-1256992191

[RidhikaJoshi]

Challenge-25

Currently working on the issue (Kadanes Algorithm in Cpp) found yesterday but this issue is not assigned to me and exploring other issues which matches my level of expertise.

[RidhikaJoshi]

Challenge-26

Today I learned about what is hacktoberfest exactly is and I am going to register in that for sure once timer stops. Joined hacktoberfest discord server. Still the previous issue is not assigned to me .

Asked the maintainer to assign me this issue.

[kuraakhilesh8230]

congrats you have completed milestone-3 successfully and you are good to go🎉

[RidhikaJoshi]

Challenge-27

I have been assigned this issue-https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/issues/181

I registered as a contributor in the hactoberfest

Tips to be kept in mind as a contributor for hactoberfest --

Find out the repositories with hacktoberfest tag and contribute in that.

Make 4 pull/merge requests accepted in the month of October to complete Hacktoberfest.

PRs must be made to a public, unarchived repository.

If all goes good and all four of your pull requests are approved, you will receive an email from the Hacktoberfest organisers with instructions on how to collect your reward after the 14-day review period.

It is the correct time now to start searching for the repositories with hacktober tag.

[RidhikaJoshi]

Challenge-28

Created a pull request for the issue- https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/issues/181

Pull request link-https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/197

[RidhikaJoshi]

Challenge-29

PR got merged- https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/197

Some Upvoted Ideas

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

2.https://github.com/scaleracademy/open-source-projects/discussions/45

[RidhikaJoshi]

Challenge-30

Successfully completed all the challenges. Thanks to Scaler for organizing it, everyone in the community was helpful and encouraged a lot during these 30 days. It was a great learning experience with Scaler Open-Source. As I was a beginner to GitHub so I didn't have even the basic knowledge of using GitHub, but due to these challenges only I was able to learn and understand many new and important things. Lastly,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 ✅