Challenge #1 - anishaga

[anishaga]

name: Anish Agarwal github_user_name: anishaga discord_id: anishaga

[anishaga]

Day2

Cloned Repo: https://github.com/anishaga/scaler-open-source-september-challenge

[anishaga]

Day3

[anishaga]

Day4

[anishaga]

Day 5

PR: Click Here

[anishaga]

Day6

[anishaga]

Day7

Added new Markdown file:

Reset Commit:

[anishaga]

Day8

[anishaga]

Log After Pushing:

Log After Squash Rebase:

Pushed on remote:

[anishaga]

Day10

Log Before Rebase: Rebase: Log After Rebase Changes Reflecting In PR

[anishaga]

Day11

[anishaga]

Day12

[anishaga]

Day13

[anishaga]

Day14

Log Before Rebase:

Rebase

Commit

[anishaga]

Day15

[anishaga]

Day16

[anishaga]

Day17

[anishaga]

Day18

[anishaga]

Day19

Changes on Repo:

GitHub Codespaces is a powerful cloud-based development environment. Basically in short it is VS code integrated in a web browser that makes it really cool. Very easy and seamless to use with all the libraries pre installed.

[anishaga]

[anishaga]

Day21

[anishaga]

Day22

[anishaga]

Day23

[anishaga]

Effective Open Source Contribution Best Practices:

1. Issue Triage:

   • Thoroughly Understand the Project: Before contributing, take time to understand the project's goals, guidelines, and existing issues.
   • Search for Existing Issues: Check if your intended contribution (bug fix, feature request, etc.) is already reported in existing issues.
   • Create Clear and Detailed Issues: If the issue doesn't exist, create a new one. Ensure it has a descriptive title, clear steps to reproduce the problem, and any relevant information about the environment (OS, software versions, etc.).
   • Label and Categorize Issues: Assign appropriate labels and categories to help other contributors and maintainers understand the issue's nature.

2. Branch Naming Conventions:

   • Use Descriptive Names: Choose branch names that are clear and descriptive of the changes you're making. Typically, the convention is to prefix with "feature/", "bug/", or similar to indicate the purpose.
   • Keep It Concise: Avoid overly long branch names. Aim for brevity while still conveying the branch's purpose.

3. Pull Request Creation:

   • Clear Title and Description: Write a concise but informative title for your pull request (PR). The description should explain what the PR does, how it addresses the issue, and any relevant context.
   • Link to Issue: Always link your PR to the related issue(s) for better traceability.
   • Small, Focused PRs: Keep PRs focused on one specific change or feature. Avoid bundling unrelated changes into a single PR.
   • Testing: Ensure your code is well-tested, and if applicable, provide test cases to validate the changes.
   • Follow Project Guidelines: Adhere to the coding style, formatting, and other guidelines specified by the project.
   • Discuss and Address Feedback: Be open to feedback from maintainers and other contributors. Discuss and make necessary changes to your PR.
   • Squash Commits: If you have multiple commits, consider squashing them into a single, coherent commit before merging.

4. Code of Conduct and Licensing:

   • Adhere to the Project's Code of Conduct: Always respect the project's code of conduct and be respectful and professional in your interactions.
   • Respect Licensing: Ensure your contributions are compliant with the project's licensing terms. Respect intellectual property rights.

5. Documentation and Communication:

   • Update Documentation: If your contribution involves changes to documentation, make sure to update the documentation accordingly.
   • Effective Communication: Be responsive and respectful when communicating with other contributors and maintainers.

[anishaga]

Day25

I've just started exploring open source projects at https://goodfirstissue.dev/ as well on GitHub, but currently, I haven't found any issues for me to work on yet. I'm actively looking for suitable issues to work on by going through the projects.

[anishaga]

Day26

For today's task I continued my search for some good first issues and found some to contribute. Today I have explored the project files to get an idea about the contribution to be made. Still searching for more good first issue in which can contribute. Also registered for the hackathon.

[anishaga]

Day27

[anishaga]

Day28

• Registered for hacktoberfest [✓]
• Raised an open source PR- https://github.com/hellofaizan/xprofile/pull/104

[hellofaizan]

Man you are very disciplined. All the best ❤️

[anishaga]

Man you are very disciplined. All the best ❤️

Thank you for the kind words :)

[anishaga]

Day29