Challenge 1 - 30(Completed) : Harshit Joshi

[Harshit-3905]

name: Harshit Joshi github_user_name: Harshit_3905 discord_id: harshitjoshi

[Harshit-3905]

Task 2: URL of Forked Repo : https://github.com/Harshit-3905/scaler-open-source-september-challenge

[Harshit-3905]

Challenge 3 :

[Harshit-3905]

Challenge 4:

[Harshit-3905]

Challenge 6:

[Harshit-3905]

Challenge 7:

[Harshit-3905]

Challenge 8:

[Harshit-3905]

Challenge 9: Before After

[Harshit-3905]

Challenge 10:

[Harshit-3905]

Challenge 11:

[Harshit-3905]

Challenge 12:

[Harshit-3905]

Challenge 13:

[Harshit-3905]

Challenge 14 : Before: After:

[Harshit-3905]

Challenge 15:

Before Resolving Merge conflict

Resolving Merge Conflict

After

[Harshit-3905]

Challenge 16:

[Harshit-3905]

Challenge 17:

[Harshit-3905]

Challenge 18:

Creating a Github Repo

Cloning the repo with the help of Github Desktop

Committing and Pushing Changes in the Local Repo

Creating Branch using Github Desktop

Pushing new_branch to Github

[Harshit-3905]

Challenge 19:

It's a great experience to work with Github Codespaces .

[Harshit-3905]

Challenge 20 :

Repo Link : https://github.com/Harshit-3905/Challenge_20_Open_Source_September

Overall, this experience highlighted the power of automation in maintaining clean and standardized codebases within a collaborative development environment.

[Harshit-3905]

Challenge 21

[Harshit-3905]

Challenge 22:

[Harshit-3905]

Challenge 23:

[Harshit-3905]

Challenge 24:

Effective Open-Source Contribution Guidelines

For Beginners:

• Start with a Beginner-Friendly Issue: If you're new to open-source contribution, begin by tackling issues labeled as "good-first-issue."

• Creating New Issues: If you wish to make changes or discover a bug not covered by existing issues, create a new issue describing the problem and wait for it to be assigned to you.

For Pull Requests (PRs):

• Write a Clear Description: When submitting a PR, provide a clear and concise description of your changes. Explain what the PR does and why it's important.

• Reference the Related Issue: Always reference the issue that your PR addresses. This links your PR to the broader context of the project.

• Review Your Changes: Before creating a PR, review your code changes thoroughly. Ensure they adhere to project coding standards and do not introduce new issues.

General Tips:

• Name Your Feature Branch Descriptively: Give your feature branch a meaningful and descriptive name that reflects the purpose of your changes.

• Use Descriptive Titles: Write descriptive and active titles for your commits and PRs. This helps others understand the purpose of each change at a glance.

• Streamline PR Creation: Establish a consistent process for creating new PRs, including naming conventions and a checklist of steps to follow.

• Provide a Meaningful PR Description: In your PR description, explain what the change accomplishes, any potential impact, and any specific steps required for testing or reviewing.

• Visual Documentation: Whenever possible, include visual documentation or screenshots to demonstrate the functionality of your changes. This makes it easier for reviewers to understand your work.

• Self-Review: Before assigning your PR to others for review, perform a comprehensive self-review. Verify that your code is well-documented, follows coding guidelines, and fulfills the intended purpose.

By following these guidelines, you can contribute effectively to open-source projects and collaborate seamlessly with the community.

[Harshit-3905]

Challenge 25:

I've started exploring open source projects at https://goodfirstissue.dev/, but currently I haven't found any good issues to work on yet. I've made a list of possible projects, and I'm actively looking for suitable issues to work on

[Harshit-3905]

Challenge 26:

1. Registered for Scalar Open Quest Hackathon
2. Still Searching for Open Source Projects

[Harshit-3905]

Challenge 27:

[Harshit-3905]

Challenge 28

1. Still Searching for an issue
2. Registered for Hacktoberfest

[Harshit-3905]

Challenge 29:

Added Readme

[Harshit-3905]

Challenge 30

I wanted to reach out and extend my heartfelt thanks to you for spearheading Open Source September. Your efforts have made a significant impact, and I appreciate all the hard work you put into making this event a reality.

Open Source September has been a remarkable experience for me, and I have gained valuable insights and skills throughout the month. Your dedication to open source and the community is truly commendable.

Thank You