Challenge#1 - 30 -SuhaibRSQSI

[SuhaibRSQSI]

name: SuhaibMohamed github_user_name: SuhaibRSQSI discord_id: salty#0363

[SuhaibRSQSI]

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

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

challenge 11 completed

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

Challenge 15 completed

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

[SuhaibRSQSI]

Challenge 21 completed

[SuhaibRSQSI]

Challenge 22 completed

[SuhaibRSQSI]

Challenge 23 completed

[SuhaibRSQSI]

Challenge 24 completed

Git Branch Naming Conventions:

• Use descriptive names that clearly describe the purpose of the branch.
• Differentiate between regular and temporary branches, and use consistent prefixes like "feature," "bug," or "hotfix" to categorize them.
• Employ hyphens or slashes as separators in branch names to enhance readability and maintain a consistent naming structure.
• Avoid making branch names overly complex by using too many conventions or including too much information.

Building a Great Pull Request:

• Use pull request titles that succinctly describe the purpose of the changes, providing a clear indication of what the PR addresses.
• Review your own pull request before seeking feedback from others, catching any issues or making improvements based on project guidelines.

Contributing Code:

• Look for issues with specific tags like 'help wanted' or 'good first issue' to find tasks intended for community contributions.
• Avoid working on issues marked 'staff only' or issues with tags like 'status: blocked' that are typically not meant for community contributions.
• When you decide to work on an issue, actively communicate your intent by commenting on the issue, reducing the chances of duplicate efforts.
• Be open to feedback on your pull requests and engage in collaborative discussions with reviewers to improve the quality of your contributions.

Creating a New Issue:

• If you can't find a suitable issue, don't hesitate to create a new one to propose changes or report problems, ensuring the project's continuous improvement.
• Be patient and open to feedback from the community when you create a new issue, as discussions may refine the scope and details of the proposed change.

[SuhaibRSQSI]

Challenge 25 completed

• Explored open source projects
• Reviewed "good first issues"
• Recognized the need for a deeper understanding of project documentation
• Committed to exploring and contributing to open source
• Thankful for the opportunity and eager to make valuable contributions

[SuhaibRSQSI]

Challenge 26 completed

• Explored good first issues and compiled a list of candidates.
• Studied CONTRIBUTING.MD files and reinforced understanding of GitHub commands and core concepts.
• Curated a collection of active repositories enthusiastic about open-source contributions.
• Reached out to project maintainers to inquire about unresolved issues and express eagerness to collaborate.
• Actively developing technical skill set to lay groundwork for creating own open-source project.

[SuhaibRSQSI]

Challenge 27 completed

[SuhaibRSQSI]

Challenge 28 completed Link of repo : https://github.com/firstcontributions/first-contributions

PR merged : https://github.com/firstcontributions/first-contributions/pull/74202

[SuhaibRSQSI]

Challenge 29

link : https://github.com/SuhaibRSQSI/suhaib.github.io