Pull Requests/Merging

Information from The State of Sarkhan Official Records

Ah, the sweet, sweet joy of merging a PR—it’s like the digital version of crossing a finish line, and it feels good, doesn’t it? There are a few psychological and procedural reasons why merging a PR to the main branch can give a developer that warm, fuzzy feeling:

1️⃣ Sense of Accomplishment

Merging a Pull Requests is like the culmination of a task. It’s actionable closure. You've worked on a problem, written code, made sure it’s ready for prime time, and now boom, it’s officially part of the project. That big green button saying "Merge" feels like victory! You’ve shipped a change, you’ve made progress, and now you can (metaphorically) rest for a moment before moving on to the next challenge.

2️⃣ The Thrill of Closing an Issue

When you merge a PR, especially if it’s tied to a specific issue, you’re not just merging code—you’re also closing the issue. It’s a double win! The issue that’s been hanging around in the tracker, the one that’s been bothering everyone, is now marked as "closed." 🎉

It’s kind of like going on a hunt and coming back with a trophy. You not only finished coding the solution but also directly contributed to progressing the project. There’s something intrinsically satisfying about completing tasks.

3️⃣ Validation from Peers

A PR merge isn’t just about what you did; it’s also about validation from your team. Once the PR is merged, the code has been reviewed, discussed, and (hopefully) approved by others. This gives you a bit of reassurance that you’re on the right track. Your peers (or the project maintainers) have acknowledged your work, which, for many developers, is like a form of positive reinforcement.

4️⃣ Movement in the Project

When you merge, it feels like you’re actively moving the project forward. Projects can stagnate sometimes, and each merge is like pushing the metaphorical boulder up the hill. Even though it’s just a small change, it feels like it contributes to the bigger picture and pushes things closer to completion. This is progress you can see!

5️⃣ It's an Act of Ownership

Merging your own PR (especially after you’ve put in the work and passed review) gives you a sense of ownership. It’s your stamp of approval. It’s a small gesture that says, "I am contributing to this project’s evolution."


TL;DR:

Merging a PR feels good because it's a small accomplishment and a sense of closure—you’ve solved a problem, closed an issue, and moved the project forward. Add in the fact that it validates your efforts with team approval, and it’s a recipe for that moment of triumph!