[ENHANCEMENT]: Create a "First Contribution Walkthrough" Guide for New Contributors

[Gunjan10-droid]

Problem Statement

While this repository provides beginner-friendly issues, many first-time contributors may still be unfamiliar with the complete open-source contribution workflow.

New contributors often struggle with:

Forking repositories correctly
Creating branches
Making commits with meaningful messages
Syncing forks with upstream repositories
Creating pull requests
Responding to review feedback

Currently, this information is either scattered across multiple resources or not available in a single beginner-focused guide.

Proposed Solution

Create a dedicated document named FIRST_CONTRIBUTION_GUIDE.md that provides a step-by-step walkthrough of the entire contribution process.

The guide should include:

Forking the repository
Cloning locally
Creating a feature branch
Making changes
Committing changes
Pushing to GitHub
Opening a Pull Request
Addressing review comments
Updating branches after changes are requested

This enhancement focuses on contributor education and documentation rather than repository configuration, making it fully achievable through a standard pull request.

Alternatives Considered

No response

Additional Context

No response

[Gunjan10-droid]

@Adez017 would you assign me this issue for nsoc26?

[Adez017]

Hi @Gunjan10-droid i think we already had this all instructions and creating the second one makes it redundant , if you are willing to add a detailed guide with real screenshots with proper naming convention , we can think about it . let me know your thoughts on this

[nike750]

Hi @Gunjan10-droid
Can you assign this issue to me, I'm a contributor in NSoC'26

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 15 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions!

[Adez017]

@nike750 go ahead an read the comment first before proceeding

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 15 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions!