#Challenge 1 @anurag-327

[anurag-327]

name: Anurag Srivastav
github_user_name: anurag-327
discord_id: anuragsrivastav

[anurag-327]

challenge #3

[anurag-327]

challenge #4

[anurag-327]

challenge #7 completed

[anurag-327]

challenge #2 issue link : #464

[anurag-327]

challenge #9

[anurag-327]

challenge #10

[anurag-327]

challenge #11

[anurag-327]

chellenge#15 completed

[anurag-327]

challenge 16

[anurag-327]

challenge 17

[anurag-327]

challenge #18

[anurag-327]

challenge 19
Working with codespaces makes collaboration easier without thinking about local git repository and without thinking of pulling and updating branches every time we want to work on some new feature.

[anurag-327]

challenge 20
It was great working with workflows...
Workflows automatically checked the code at each code thus improving the quality of code..

[anurag-327]

challenge 21

[anurag-327]

challenge 22

[anurag-327]

Challenge 24

In the Git version control system, branches are divided into two types: regular branches and temporary branches; Each branch has a specific purpose. A well-known organizational structure is important for transparency and organization. Maintaining proper branch management and journaling recommendations is critical to maintaining Git's functionality and evolution.

Git Branching Strategies:

###Regular Branches:
Regular branches, which include development, main and QA branches, play a role in the project

• Dev: Main development branch.
• Master: Stable default branch.
• QA: For testing before production.

Temporary Branches:

Temporary branches, such as bug fixes and tree branches, are created based on the needs of a particular task or feature

• Bug Fix: Fixes for specific issues.
• Hot Fix: Urgent critical fixes.
• Feature: For new features.
• Experimental: For experiments.
• WIP: Work in Progress.

Git Branch Naming Conventions:

 * Start with a Group Word: Prefix with "Bug" or "WIP" for clarity.
 * Use Unique ID: Include issue tracker IDs for task association.
 * Use Separators: Choose hyphen, slash, or underscore consistently.
 * Include Author Name: Optionally, for tracking contributors.
 * Avoid Numbers Only: Numeric branch names lack context.
 * Avoid Mixing Conventions: Stick to one naming style.
 * Keep Long-Lived Names Precise: Descriptive but not overly long

Proper branch management and naming conventions are crucial for efficient Git workflows.

TIP 1: Give your feature branch a clear name, and consider prefixing it with your initials for clarity and easy filtering.
TIP 2: Use active and descriptive titles for commits and PRs, and consider using the imperative tense. Add "WIP:" or "IN PROGRESS:" prefix if the PR is not ready for review.
TIP 3: Streamline PR creation with a bash function or hub user commands to push, open, and create PRs quickly.
TIP 4: Provide a meaningful PR description with "Why," "How," and "What" sections to help reviewers understand the changes.
TIP 5: Show functionality visually using screenshots and GIFs in your PR description.
TIP 6: Review your own PR before you assign it to others.

To find out which issues need to be addressed in a project, see the GitHub issues section associated with each project. Tags indicate topics that are open to community participation. Once you select an issue, comment on it, submit a pull request, wait for review, and collaborate with others. If you are creating a new issue, please create a detailed topic and wait for approval from the project manager before starting work.

[anurag-327]

challenge 25
Update:
Working to find some good first issues. Explored some repos like markdown-dungeons, docasorus, fastify, devswags.
Will be updating in the future if i get assigned some issues...

[anurag-327]

challenge 26

Still searching for some active good first issues,
Btw I have already contributed in open source contributions in SSOC (Social Summer of code 2023) and also contributed in two open source projects pint and playground...

Here are few scrrenshots

[anurag-327]

challenge 27

Before cherypick

After cherrypick

[anurag-327]

challenge 28

waiting for some a good first issue to be assigned,
Preparing myself for hacktoberfest

registered for hacktoberfest

[anurag-327]

challenge 29

[anurag-327]

challenge 30

Thank you, scaler, for this challenge💖