After a Project is assigned

[kamalesh-og]

Can anyone say what is the next step for the contributor once our request for the issue is accepted.
Like what should we do next?
Thank you.

[Chhaya-g]

Do read the read.me file to know how you are suppose to install and setup the code in your machine. Also, don't forget to follow the code of conduct. once, you setup the code in your own(local) machine, then start working on the issue which you are assigned. Once, you are done with the changes or resolving the assigned issue then create a branch and create a pull request. After this, the admin will verify your changes and merge your changes in the main project.
PS. don't forget to "star" and "fork" the repository before cloning it and setting it up in your own machine.
PPS. I am also a newbie so, forgive me if I make a mistake while guiding you.
Thankyou, Hope it helps!!!

[Princegupta101]

clone the repo and figure out the issue and make pr and add reviwers than they are check and merge it or give acess to merge the req in main code @kamalesh-og

[Ojas-Arora]

Once your request for an issue is accepted in GSSoC or any open-source project, here are the next steps you should follow:

1. Understand the Issue: Take some time to fully understand the issue you've been assigned. Make sure you understand the problem, what needs to be done to fix it, and any requirements or constraints.

2. Fork the Repository: If you haven't already, fork the repository of the project you're contributing to. This creates a copy of the repository in your GitHub account where you can make changes.

3. Clone Your Fork: Clone your forked repository to your local machine using Git. This allows you to work on the code locally.

   git clone https://github.com/your-username/repository-name.git

4. Create a New Branch: Create a new branch for your changes. This helps keep your changes isolated from the main branch and makes it easier to manage multiple contributions.

   git checkout -b your-branch-name

5. Work on the Issue: Start working on the issue by making the necessary changes to the codebase. Follow best practices for coding, documentation, and testing as applicable.

6. Commit Your Changes: Once you've made your changes, commit them to your local repository with descriptive commit messages.

   git add .
   git commit -m "Your commit message"

7. Push Your Changes: Push your changes to your forked repository on GitHub.

   git push origin your-branch-name

8. Create a Pull Request: Go to the GitHub page of your forked repository and create a pull request (PR) to merge your changes into the main repository. Provide a clear description of your changes in the PR.

9. Wait for Review: Wait for the project maintainers to review your pull request. They may provide feedback, ask for changes, or approve your changes and merge them into the main branch.

10. Address Feedback: If the maintainers request changes, address them by making additional commits to your branch and pushing the changes to your forked repository.

Remember to follow the project's contribution guidelines and any specific instructions provided by the maintainers. Communication is key, so don't hesitate to ask questions if you need clarification on anything.

[kamalesh-og]

Thank you

[sanjay-kv]

Can anyone say what is the next step for the contributor once our request for the issue is accepted. Like what should we do next? Thank you.

Please watch this :https://www.youtube.com/watch?v=Y9PYaPZgikg&t=5s