Challenge 30/30

[Rimjhim20]

name: Rimjhim Kumari github_user_name: Rimjhim20

[Rimjhim20]

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

[Rimjhim20]

Screenshot showing the list of all the current branches inside of your forked clone repository :

[Rimjhim20]

[Rimjhim20]

Challenge 8

[Rimjhim20]

Challenge 9

[Rimjhim20]

Challenge 10

[Rimjhim20]

Challenge11

[Rimjhim20]

Challenge 12

[Rimjhim20]

Challenge 13 - Git Stash

[DaltonDeven]

Good to go verified ✅

[Rimjhim20]

challenge 14

[Rimjhim20]

challenge 15

[Rimjhim20]

Challenge 16

[Rimjhim20]

Challenge 17 - repo link - https://github.com/Rimjhim20/Scalerchallenge17repo

[Rimjhim20]

Challenge 18

[Rimjhim20]

challenge 19

[Rimjhim20]

Challenge 20 Project Board - https://github.com/users/Rimjhim20/projects/1/views/1 Repo Link - https://github.com/Rimjhim20/ScalerChallenge20

[Rimjhim20]

Challenge21

[Rimjhim20]

challenge 22 repo link - https://github.com/Rimjhim20/challenge-22 hosted link- http://rimjhimweb.me/challenge-22/

[Rimjhim20]

Challenge 23

1. First find Issue - We can find the issues by using these tags [issues labeled good first issue] [issues labeled help wanted] [PRs labeled help wanted]

2. Comment to give confirmation of your work - Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue. Once the Issue is assigned to us, we can start our work.

3. Start with a clear name feature branch - A well-formed PR should start with a well-named feature branch. Developers create branches off of development for their Working on an individual feature and giving that feature branch a clear name is an important first step when collaborating with others on a single repository.

4. We Should give proper titles to our commits and PRs - It's a good idea to use the present imperative tense — for example, use “Added Responsive Navbar” instead of “Done”.

5. Descriptive PR - The more information we give to project maintainers before they look at our actual code, the easier their job will be.

6. Try to show functionality visually, whenever possible - Take screenshots and just paste these screenshots directly into your PR description on GitHub.

7. Review your own PR before you assign it to others Try to resolve any conflicts that might exist, so that merging is as easy as pressing a button. Lint our code and all DCO should be checked.

8. Submit PR and wait for code review and address any issues raised as soon as you can.

[Rimjhim20]

Challenge 24: Searching for good first issues to make beginner-friendly contributions.

Status :

Looking for more repositories and issues that are suitable for me and to which I can contribute. I explored many repository issues and commented on 1 -2 issues for approval or assignment. I will update my work.

[Rimjhim20]

Challenge 25

I have been assigned one issue and I have started working on them and will make a Pull Request for it as soon as possible.

Update - My PR is merged now for this assigned issue. Successfully contributed to one repository with a good first issue.

[Rimjhim20]

Challenge 26 - Successfully registered for Hacktoberfest 2022 and I have been awarded a Holopin badge for registering for hacktoberfest.

[DaltonDeven]

Challenge 25 pending , complete and update PR as soon as possible

[Rimjhim20]

Hey, I updated my challenge 25 plz check @DaltonDeven

[Rimjhim20]

Challenge 27 -

1. I've gone through the rules and resources provided by Hacktoberfest.
2. Explored different open source repositories and issues.
3. Will start contributing in repo 60 seconds of code in C++ which is the repository made by collaborating with Scaler discord member.

My Tips For Hacktoberfest 2022

Best practices when participating in Hacktoberfest.

1. Register anytime between September 26 and October 31
2. Pull requests can be made in any GITHUB or GITLAB hosted project that’s participating in Hacktoberfest
3. Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest

Opening a pull request in GitHub If the project is on GitHub, here’s how we can submit a pull request:

1. Fork the repository and clone it locally.
2. Connect our local to the original “upstream” repository by adding it as a remote. Pull in changes from “upstream” often so that you stay up to date so that when you submit your pull request, merge conflicts will be less likely.
3. Create a branch for your edits and push our changes on that branch only.
4. Click on contribution on GitHub and Create a pull request.
5. While creating PR make sure to add perfect comments and descriptions about all changes.
6. If possible try to attach screenshots in your PR as well. This will make it easier for the maintainer to merge, and others to understand and maintain in the future.

Happy Contribution!!

RESOURCES FOR BEGINNERS

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

PULL/MERGE REQUEST DETAILS

(i) pr/mrs must be within the bounds of hacktoberfest. (ii) repos that go against hacktoberfest’s values will be excluded from qualification and pr/mrs made to those repos won’t count. (iii) pr/mrs must not be spammy. (iv) pr/mrs must be in a repo tagged with the “hacktoberfest” topic, or be labeled “hacktoberfest-accepted.” (v) pr/mrs must not be labeled as “invalid”. (vi) pr/mrs must be merged, have the “hacktoberfest-accepted” label, or have an overall approving review. (vii) once pr/mrs pass all the checks above, it will be accepted for hacktoberfest after the 7-day review period.

Types of people in open source projects

Author: The person/s or organization that created the project Owner: The person/s who has administrative ownership over the repository Maintainers: Contributors who are responsible for managing the repo Contributors: Everyone who has contributed something back to the project Community Members: People who use the project. They might be active in conversations or express their opinion on the project’s direction

[DaltonDeven]

Verified for milestone-3 congrats...

[Rimjhim20]

Challenge 28

I contributed to 2 good first contributions till now:

https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/175 https://github.com/firstcontributions/first-contributions/pull/54695

Both of my PRs got merged successfully into the project. Also Reading some repository contribution guidelines.

I Commented for issue assignment approval in one Hacktoberfest repository and they assigned me that issue but will contribute from 1 October on that repository because that repository is archived now.

Screenshots

[Rimjhim20]

Challenge 29

I've checked out the existing ideas other community members have already shared.

Existing ideas that I commented on and upvoted.

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

My opened Discussion link - https://github.com/scaleracademy/open-source-projects/discussions/146

[Rimjhim20]

Challenge 30 (Last Day of challenge)

Also while searching for repositories I found some repo where I can contribute and go through all the details and rules of these repositories. (i) https://codeincommunity.tech/hacktoberfest2022 (ii)https://github.com/kishanrajput23/Hacktoberfest-2022 (iii)https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems (iv)https://github.com/PrakashGatiyala/60-seconds-of-cpp Also, cloned some of the repositories and started working on this repo, and will make PR soon for Hactoberfest.

My experience

This is the last day of the 30-day open source challenge. 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. And it was a nice journey for me. Thank you Scaler Community for organizing it, Specially thanks to everyone in the community who helped me and encouraged me a lot during these 30 days. No doubt, It was a great learning experience. In these 30 days, I learn new things and feel confident about open source. I hope this type of challenge comes in feature. Thanks to Scaler, and all community members.