Challenge #1: Ishita Choudhury

[ImcalledIshita]

name: Ishita Choudhury github_user_name: ImcalledIshita discord_id: ishitachoudhury

[ImcalledIshita]

URL of forked Repo: https://github.com/ImcalledIshita/scaler-open-source-september-challenge.git

[ImcalledIshita]

[ImcalledIshita]

Challenge 4

[ImcalledIshita]

Challenge 7

[ImcalledIshita]

Challenge 9

[ImcalledIshita]

Challenge 10

[ImcalledIshita]

Challenge 10

[ImcalledIshita]

[ImcalledIshita]

Challenge 12 and 13

[ImcalledIshita]

Challenge 14

[ImcalledIshita]

Challenge 15

[ImcalledIshita]

Challenge 16

[ImcalledIshita]

Challenge 17

[ImcalledIshita]

Challenge 18

[ImcalledIshita]

Challenge 19

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.

[ImcalledIshita]

Challenge 20

It helped me with clean coding and learning to contribute to a large code base and enhance code quality and consistency in collaborative projects.

[ImcalledIshita]

Challenge 21

[ImcalledIshita]

Challenge 22

[ImcalledIshita]

Challenge 24

Git Branching Strategies A branching strategy in Git is a set of rules that guide how developers create and manage branches. It helps in organizing and separating work effectively. Regular Git Branches

Development (dev): This is the main branch for ongoing development. Changes are made here and then reviewed and tested before merging into the master branch.

Master (master): The default stable branch. Direct changes aren't allowed; all updates go through code review before merging.

QA (QA): This branch is for testing all changes before they go into production. It ensures a stable codebase.

Temporary Git Branches

These branches are created and deleted as needed. They include Bug Fix, Hot Fix, Feature Branches, Experimental Branches, and Work in Progress (WIP) branches.

Naming Conventions for Branches

• Start with a Group Word: Use short, descriptive words like "bug" or "WIP" to indicate the purpose of the branch.

• Use Unique ID: Incorporate issue tracker IDs in the branch name for tracking progress.

• Use Separators: Choose either hyphens, slashes, or underscores for better readability and management.

• Include Author Name: Optionally, add the author's name to the branch name for easy tracking of contributions.

• Avoid Numbers Only: Don't rely solely on issue IDs in branch names; it can lead to confusion.

• Avoid Mixing Naming Conventions: Stick to one naming convention to maintain consistency.

• Keep Long-Lived Branch Names Precise: Avoid overly descriptive names for branches that exist for a long time.

Tips for Creating Pull Requests (PRs)

• Clear Feature Branch Names: Prefix feature branch names with initials or a relevant identifier.

• Use Descriptive Titles: Use present imperative tense in commit messages and PR titles for clarity.

• Streamline PR Creation: Use scripts or functions to push changes and open PRs efficiently.

• Provide a Meaningful Description: Explain why the code is necessary, list important commits, and demonstrate functionality.

• Visualize Functionality: Use screenshots or GIFs to give reviewers a visual overview of changes.

• Review Your Own PR: Ensure your code is up-to-date, passes tests, and adheres to coding standards.

Contributing to Open Source Projects

• Follow established guidelines for finding and working on issues. Comment on the issue you're working on to avoid conflicts.

• Propose new issues by creating a GitHub issue with implementation details and rationale.

[ImcalledIshita]

Challenge 25

Made some considerations on which tech-stacks and projects I'd like to work on which is probably going to be on Javascript mostly. Went through some CONTRIBUTING.md files as well to analyse usual workflow. Went through some issues as well and other's comments on it as well to learn more about it. Found some more websites with good first issues to checkout. I will continue to search for more projects to contribiyte to in the future.

[ImcalledIshita]

Challenge 26

Today I found an open source project that helps with your first contribution. I made a contribution, submitted a pull request and got merged. Will continue to look further for more such projects and keep updating this.

[ImcalledIshita]

Challenge 27

[ImcalledIshita]

Challenge 28

I have already contributed to one open source project yesterday and am on the lookout for more such projects. Will update once I get any.

For now, I am happy to share that I have successfully registered myself for Hacktoberfest 2023 which also celebrates the 10th anniversary of Hacktoberfest and I'm really excited to participate.

[ImcalledIshita]

Challenge 29

I have created a github profile readme