How to know contributions made by someone?

[PRATHAMU200]

When i contribute to a project and how do the ggsoc team identify or get to know that i have contributed?
Also please tell me what is PR?

[thevijayshankersharma]

When you contribute to a project, especially in open-source initiatives like Google Summer of Code (GSoC), your contributions are typically made through actions such as submitting code changes, bug fixes, documentation updates, or other improvements to the project's codebase or related resources.

To ensure that your contributions are recognized and acknowledged by the GSoC team, you typically follow the project's contribution guidelines, which may involve steps like:

Forking the Repository: Making a copy of the project's code repository on your own GitHub or GitLab account.
Making Changes: Implementing the changes or additions you want to contribute within your forked repository.
Creating a Pull Request (PR): Once your changes are ready, you submit a pull request to the original project repository. This request signals to the project maintainers that you have made changes and are suggesting that they be incorporated into the main codebase.
Review and Merge: The project maintainers review your changes, provide feedback if necessary, and eventually merge your changes into the main project if they are deemed appropriate.
Your contributions are typically tracked through this process. The GSoC team may also have their own tracking mechanisms to monitor contributions from participants. They may look at metrics like the number of pull requests submitted, the quality of contributions, the impact of your changes, and your overall engagement with the project community.

Now, to your second question: What is PR?

PR stands for "Pull Request." It's a method of submitting contributions to a code repository hosted on platforms like GitHub, GitLab, or Bitbucket. A pull request is a request to the owners of the repository to "pull" your changes into the main codebase.

Pull requests typically include details about the changes being proposed, such as the specific commits, files affected, and a description of the purpose of the changes. They allow for peer review, where other developers can provide feedback, suggest improvements, or approve the changes before they are merged into the main branch of the repository.