PR ?

[rajvaidyanath27]

Hey can anybody explain me that what it means if we raise PR after resolving an issue or raising a PR after contributing to the project. Both have the same meaning?

[aswinikalyan30]

Yes - you are contributing to the project based on the issue assigned to you

[Ojas-Arora]

Raising a pull request (PR) after resolving an issue and raising a PR after contributing to the project both involve contributing code changes to the project's repository, but they represent slightly different scenarios:

1. Raising a PR after Resolving an Issue:

• Meaning: This typically refers to submitting a pull request to the project's repository after addressing and resolving an existing issue.
• Process:
  1. Identify an issue in the project's issue tracker that you want to work on.
  2. Fork the repository, make the necessary changes in your local branch to address the issue.
  3. Push your changes to your forked repository and submit a pull request referencing the issue number.
  4. Once your PR is reviewed and approved, the changes are merged into the main project.

2. Raising a PR after Contributing to the Project:

• Meaning: This refers to submitting a pull request with contributions that may not be directly associated with a specific issue but are beneficial to the project.
• Process:
  1. Identify areas where you can contribute to the project, such as improving documentation, refactoring code, fixing minor issues not tracked in the issue tracker, or adding new features.
  2. Make the necessary changes in your local branch.
  3. Push your changes to your forked repository and submit a pull request to the main project repository.
  4. The maintainers will review your changes, provide feedback, and merge them if they meet the project's standards.

Differences:

• Focus: Raising a PR after resolving an issue is more focused on addressing a specific problem documented in the issue tracker. Raising a PR after contributing to the project can involve a wider range of contributions, including those not directly tied to existing issues.
• Tracking: PRs raised after resolving issues are often linked directly to the issue they address, making it easier to track the resolution of specific problems. PRs raised after contributing to the project may not be tied to a specific issue but are still valuable contributions.

In summary, while both scenarios involve submitting pull requests with code changes, raising a PR after resolving an issue is more targeted towards specific problems documented in the issue tracker, whereas raising a PR after contributing to the project encompasses a broader range of contributions.

[sanjay-kv]

@Ojas-Arora This looks like AI bot answer. please don't do this to get badges. Opensource is about how efficient you answer and contribute.

[aswinikalyan30]

Seen multiple of these across the discussions unfortunately

[SpaciousCoder78]

Yeah this guy just pastes ChatGPT answers everywhere.

If you don't have anything to offer on your own, just stay silent.

[iHRex]

Hello @rajvaidyanath27

In Open Source, we use PR as an abbreviation for PULL REQUEST. I'd request you to kindly go through the sample video: https://www.youtube.com/watch?v=rgbCcBNZcdQ

Hope it helps

[ishankumax]

Both scenarios entail proposing changes through a pull request, whether it's addressing specific issues or contributing to the project in various ways.

Check the below points for a better understanding :
Absolutely:

• Raising a PR after resolving an issue" and "raising a PR after contributing to the project" essentially mean the same thing.
• It involves proposing changes to the project's codebase through a pull request.
• In the first scenario, changes specifically address identified issues.
• In the second scenario, contributions could range from adding features to fixing bugs or updating documentation.
• Both scenarios aim to submit changes for review and integration into the project.

[Piyushsahu99]

Raising a pull request (PR) after resolving an issue and raising a PR after contributing to the project can have similar meanings, but they may involve slightly different contexts:

1. Raising a PR after resolving an issue: This typically means that you've identified an issue in the project, whether it's a bug, an enhancement, or a feature request. You've then worked on resolving or addressing that issue by making changes to the codebase. Once you've completed your work, you create a pull request to propose your changes for review and integration into the project.

2. Raising a PR after contributing to the project: This can refer to a broader range of contributions beyond just resolving specific issues. It could include tasks such as improving documentation, refactoring code, optimizing performance, or adding new features that weren't necessarily tied to a specific issue. Similar to resolving an issue, you create a pull request to submit your changes for review and inclusion in the project.

In both cases, the ultimate goal of raising a PR is to contribute your changes back to the project in a way that allows them to be reviewed, discussed, and eventually merged into the main codebase. Whether you're addressing a specific issue or making more general contributions, the PR serves as a means of communication and collaboration with the project maintainers and other contributors.

[ishita-43]

Hey there! So, when you raise a PR (pull request) after resolving an issue or contributing to a project, it's kinda of like saying, "Hey, I've made some changes or fixes, take a look! " It's a way to show the project maintainers what you've done and ask for your changes to be reviewed and eventually merged into the main codebase. Whether you're fixing a bug or adding a new feature, raising a PR is your way of sharing your work with the project team. So yeah, in a nutshell, both scenarios pretty much have the same idea behind them. Hope that clears things up! 🚀
If you are wondering how to make PR then please refer:-
(https://github.com/GSSoC24/Contributor)

And on this page when they say contribute to the project they simply mean you can contribute to the project (make changes to the project I. e. Bug, new features, documentation updates etc. ) through a step-by-step process from first cloning/forking the desired repository into your account and lastly making pull requests also called PR.
So Pull requests are last part of project contribution as a whole .