Challenge #1 - Rohit Mekhe

[RoHiTMeKhE]

name: Rohit Mekhe github_user_name: RoHiTMeKhE discord_id: rohitmekhe

[RoHiTMeKhE]

URL of your forked repositor : https://github.com/RoHiTMeKhE/scaler-open-source-september-challenge.git

[RoHiTMeKhE]

Screenshot of all current branches inside my forked clone repository:

[RoHiTMeKhE]

Challenge 4 : All contents of my local repository are now in sync with upstream.

[RoHiTMeKhE]

Completed challenge 5

[RoHiTMeKhE]

Completed challenge 6 Link to the commit in pull request->https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/794/commits/34a51faa5acf00f6484a4a714dc8cda1cc57b575

[RoHiTMeKhE]

Completed challenge 7 Link to pull request->https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/794 Scrteenshot:-

[RoHiTMeKhE]

Completed challenge 8: Screenshot of complition:

[RoHiTMeKhE]

Challenge 9 completed.

Screenshot 1 - commiting change and pushing to github.

Screenshot 2 - pick and squash

Screenshot 3 - the commit message

Screenhot 4 - force pushing the squashed commit to github

[RoHiTMeKhE]

Challenge 10 completed. Screenshot 1 -pushing changes to github in RoHiTMeKhE-details branch

Screenshot 2- Syncing the local system

Screenshot 3 - git rebase command

Screenshot 4 - squashing and picking commits

Screenshot 5- force pushing the changes

Screenshot 6 - changes visible on github in pull request

[RoHiTMeKhE]

Challenge 11 done

[RoHiTMeKhE]

Challenge 12 completed. screenshot 1:

screenshot 2:

screenshot 3:

[RoHiTMeKhE]

Challenge 13 completed: Link to file where 2 gists link is added: https://github.com/RoHiTMeKhE/scaler-open-source-september-challenge/commit/4dde88a46dda6c858b09e39034e7df38fb3cf79a

screenshot of git bash:

[RoHiTMeKhE]

Challenge 14 completed:

pull screenshot:

[RoHiTMeKhE]

Challenge 15 completed:

[RoHiTMeKhE]

Challenge 16 completed:

[RoHiTMeKhE]

Challenge 17 completed:

Screenshot of conflict resolved :

Screenshot of Changes reflected in pull request on github.

[RoHiTMeKhE]

Challenge 18 completed

Creating new repository on GitHub:

Cloning the repo with the help of GitHub Desktop

Created a new Markdown in local repo

Committing and Pushing changes:

Publishing the new branch to the origin:

[RoHiTMeKhE]

Challenge 19 completed :

GitHub Codespaces is a powerful cloud-based development environment that allows seamless coding directly within your web browser. It provides a pre-configured workspace with code editing, terminal access, and integrated tools, eliminating the need for local setup. Codespaces promotes collaborative development, enabling teams to work together effortlessly on projects.

[RoHiTMeKhE]

Challenge 20 completed.

[RoHiTMeKhE]

Challenge 21 completed. Step 1: Todo list

Step 2: In Progress

Step 3: Done/Completed

[RoHiTMeKhE]

Challenge 22 completed.

Configuring and using shortcuts for commands:

[RoHiTMeKhE]

Challenge 23 completed.

Updated the file with link:

Website :

[RoHiTMeKhE]

Challenge 24 completed.

Understanding CONTRIBUTING.md:

Check for CONTRIBUTING.md: Before you start contributing to an open-source project, always check if there is a file named CONTRIBUTING.md in the repository. This file usually contains guidelines and instructions for contributors. Effective Open Source Issue Creation:

Clear and Descriptive Titles: When creating an issue, make sure to use a clear and descriptive title. This helps other contributors and maintainers understand what the issue is about at a glance. Provide Context: In the issue description, provide sufficient context about the problem or feature request. Include steps to reproduce if it's a bug, or explain the desired functionality if it's a feature request. Labeling: Use labels to categorize issues. Labels can include things like bug, enhancement, documentation, etc. This helps in organizing and prioritizing issues. Linking Issues and Pull Requests: Use keywords like "closes", "fixes", or "resolves" followed by the issue number to automatically link the issue to a pull request when it's merged. Git Branch Naming Conventions:

Use Descriptive Names: When creating a new branch, use a name that clearly indicates what the branch is about. This makes it easier for others to understand the purpose of the branch. Avoid Special Characters and Spaces: Stick to alphanumeric characters and hyphens. Avoid spaces or special characters in branch names. Pull Request Creation:

Clear and Concise Titles: Similar to issues, provide a clear and concise title for your pull request. It should indicate what changes are being made. Detailed Description: Provide a detailed description of the changes made in the pull request. Explain why these changes are necessary and how they address the issue. Link to Related Issues: If your pull request is related to an existing issue, make sure to reference it in the description. Use keywords like "closes", "fixes", or "resolves". Reviewers and Assignees: Specify reviewers and assignees for the pull request. This helps in getting timely feedback. Code Quality and Style:

Follow Code Guidelines: Adhere to the coding standards and style guide of the project. Consistency in code style is crucial for maintainability. Testing:

Include Tests: If applicable, include tests for the changes you've made. This helps ensure that your code is robust and doesn't introduce new issues. Documentation:

Update Documentation: If your changes affect documentation, make sure to update it accordingly. Continuous Integration (CI):

Ensure CI Passes: Before submitting a pull request, ensure that the Continuous Integration tests pass. This helps maintain code quality. Be Courteous and Respectful:

Be Respectful in Discussions: When interacting with other contributors or maintainers, be respectful and considerate. Provide constructive feedback and be open to suggestions. Patience and Persistence:

Be Patient: Understand that contributions may take time to get reviewed and merged. Be persistent and open to making necessary changes based on feedback.

[RoHiTMeKhE]

Challenge 25 completed.

I've been looking at various open-source projects on the website https://goodfirstissue.dev/ but I haven't been able to find one that matches my technical skills and is beginner-friendly. It's been a bit challenging to find the right project to work on, but I'm determined to keep searching for opportunities to contribute to real projects. Finding a suitable "good first issue" is not easy, but I'll continue my search, and hopefully, I'll find a project I can contribute to by [tomorrow.

[RoHiTMeKhE]

Challenge 26 completed.

Still the search continues..im trying hard to find one good open source..but still not yet found. will update here once got.

[RoHiTMeKhE]

Challenge 27 Completed.

[RoHiTMeKhE]

Challenge 28 Completed.

Yesterday i registered for hactberfest and im still looking for somewhere to contribute..As it was not mentioned in task to update it in issue so not updated here..

[RoHiTMeKhE]

Challenge 29 Completed. Created my profile readme : https://github.com/RoHiTMeKhE