DEV Community

Cover image for 6 differences you must know between a Good Pull Request (PR) Vs a Bad Pull Request (PR)
Pragyan Tripathi
Pragyan Tripathi

Posted on

6 differences you must know between a Good Pull Request (PR) Vs a Bad Pull Request (PR)

Are you tired of submitting pull requests that never get merged or receiving pull requests that are difficult to review?

Pull Requests (PRs) are an integral part of the collaborative process in software development. They enable developers to submit their changes to a codebase for review and feedback and to merge those changes into the main codebase. However, not all PRs are created equal. Some are well-crafted, well-organized, and easy to review, while others are confusing, poorly formatted, and frustrating to work with.

Here are 6 differences you must know between Good Pull Request Vs Bad Pull Request:

Difference 1

Good Pull Request is well written and clearly explains the changes being proposed. Vs Bad PR is poorly written or vague about the changes being made.

Difference 2

Good PR includes how the changes have been tested makes us go faster in the long run. Vs Bad PR may not be tested or may include inadequate testing information.

Difference 3

Good PR is focused and addresses a single issue. Vs Bad PR addresses multiple issues at once.

Difference 4

Good PR is based on the latest version of the codebase. Vs Bad PR is based on an outdated version of the codebase.

Difference 5

Good PR has a faster review and approval cycle. Vs In Bad PR, review or approval takes a longer time.

Difference 6

Good PR is easy to merge and does not cause conflicts with other changes. Bad PR causes conflicts or is difficult to merge due to a lack of attention to detail.

Image description

Thanks for reading this.

If you have an idea and want to build your product around it, schedule a call with me.

If you want to learn more about DevOps and Backend space, follow me.

If you want to connect, reach out to me on Twitter and LinkedIn.

Top comments (0)