Challenge #1 Komal Gawade

[Gawade15]

name:Komal Ashok Gawade github_user_name: Gawade15 discord_id: KGawade_15#1739

[Gawade15]

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

[Gawade15]

Task #3 completed

[Gawade15]

Task #4 Completed

[Gawade15]

Task #5 completed

[Gawade15]

Task #6 completed

[Gawade15]

Task #7 completed

[Gawade15]

Task #8 completed

[Gawade15]

Task #9 completed

[Gawade15]

Task #10 completed

[Gawade15]

Task #11 Completed

[Gawade15]

Task #12 completed

[Gawade15]

Task #13 completed

[Gawade15]

Task #14 completed

[Gawade15]

Task #15 completed

[Gawade15]

Task #16 completed

[Gawade15]

Task #17 completed

[Gawade15]

Task #18 completed

[Gawade15]

Task #19 completed Today first time i used Github Codespace , modified file created in previous challenge and pushed the changes to the repository . Experience: GitHub Codespaces provide feature to write and edit code directly in your browser without the need to set up a local development environment. This is especially useful for collaborating on code with team members, as everyone can access the same environment and codebase.

[Gawade15]

Task #20 completed Experience: This GitHub Actions workflow will check your code for linting issues whenever changes are pushed to the main branch. If there are any linting errors, the workflow will fail and notify you.

[Gawade15]

Task #21 completed

[Gawade15]

Task #22 completed

[Gawade15]

Task #23 completed

[Gawade15]

Task #24 completed

Key points for effectively contributing to open source project :

Use Simple, Descriptive Names: Avoid using numeric or overly long branch names in your Git repository to prevent confusion among team members.

Hyphens for Readability: Instead, opt for shorter, descriptive names that are easy to understand. Use hyphens as separators in branch names to enhance readability and maintain simplicity. This approach helps keep the branch names concise and effective during project development.

Branch Names: •Use clear and concise names for feature branches. •Consider adding your initials as a prefix for clarity.

Titles: •Use active, descriptive titles for commits and PRs. •Avoid vague or passive language.

PR Descriptions: •Explain why code changes are needed. •List important commits and their purpose. •Use images or GIFs to demonstrate functionality.

Finding an Issue: •Check GitHub issues for tasks. •Look for "help wanted" or "good first issue" labels. •Avoid "staff only" or certain status-labeled issues.

Contribution Process: •Comment on the chosen issue. •Write code, submit a pull request, and respond to reviews.

Proposing a New Issue: •Create a GitHub issue with details. •Await approval before starting work.

[Gawade15]

Task #25 completed As a beginner in open-source contribution, I am currently exploring the open-source and searching for a project that is suitable for me and match my tech stack . I will continue searching until I find the right one.

[Gawade15]

I completed Task #26 today. Continuing from yesterday's task, I discovered an open-source project that I'm interested in contributing to. I've submitted an issue to the project's author and hope that it will be accepted soon. Feeling excited about making my contribution! ✌️

[Gawade15]

Task #27 completed

[Gawade15]

Task #28 completed I haven't received a reply from the author regarding my issue. I am now searching for more repositories to contribute to Registered Successfully For Hacktoberfest 2023

[Gawade15]

Task #29 Completed

[Gawade15]

Task #30 completed 🌟 Completed #OpenSourceSeptember! 🚀 I'm thrilled to share that I've completed the #OpenSourceSeptember challenge, and it's been an incredible journey of learning, collaborating, and giving back to the open source community. 🙌