Challenge #1-Brijesh

[BRijesh2001singh]

name: Brijesh Singh github_user_name: BRijesh2001singh discord_id: brijesh3350

[BRijesh2001singh]

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

[BRijesh2001singh]

[BRijesh2001singh]

[BRijesh2001singh]

CREATED NEW FILE

GIT RESET TO PREVIOUS COMMIT

[BRijesh2001singh]

[BRijesh2001singh]

[BRijesh2001singh]

challenege 11 completed

[BRijesh2001singh]

MERGE CONFLICT

MERGE CONFLICT SOLVED

Challenge 15 completed

[BRijesh2001singh]

challenge 17 completed

[BRijesh2001singh]

challenge 18 completed!!

[BRijesh2001singh]

//USED GITHUB CODESPACE

GITHUB CODE BASE EXPERIENCE :my first experience with GitHub Codespaces was positive. It eliminated many of the initial complexities I usually faced when setting up a development environment. It offers a hassle-free way to start coding quickly, collaborate effectively, and work from anywhere with an internet connection

challenge 19 completed!!

[BRijesh2001singh]

Created hello.py

Workflow passed

challenge 20 completed!!

[BRijesh2001singh]

challenge 21 completed!

[BRijesh2001singh]

challenge 22 done !

[BRijesh2001singh]

challenge 23 done!

[BRijesh2001singh]

challenge 24 done! Open Source Issue Creation: Before creating an issue, thoroughly understand the project's goals, existing issues, and the feature/bug you want to address. Ensure your contribution aligns with the project's objectives. Check if the issue you want to report or work on already exists. Duplicates can be a waste of time and resources. If it does exist, consider adding additional information or offering to help with it. When creating a new issue, provide a clear and concise description. Include relevant information like the problem, expected behavior, and steps to reproduce the issue. Clarity is essential for developers who may work on the issue. Use appropriate labels or tags to categorize the issue (e.g., bug, enhancement, documentation). This helps maintainers and contributors quickly find relevant tasks.

Branch and Pull Request Creation: If you're not a project collaborator, fork the repository to your GitHub account. This creates a copy you can work on. Create a new branch for each feature or bug fix you're working on. Use descriptive names for branches (e.g., fix-issue-123 or feature-new-feature). Keep your forked repository up-to-date with the main project's changes by syncing your fork regularly. This avoids conflicts when you submit a pull request. When you're ready to contribute, create a pull request. Provide context, explain the changes, and reference the relevant issue. ce. Testing and Documentation: Ensure your changes are well-tested, and update documentation if needed. A good contribution not only fixes issues but also ensures they don't reoccur.

[BRijesh2001singh]

Resolved an issue. challenge 26 completed !

[BRijesh2001singh]

challenge 27 done!

[BRijesh2001singh]

created github profile challenge 29 done!