---
title: "#pr articles | Hashnode"
description: "Explore 18 articles tagged #pr on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/pr"
---

Tag

# #pr

18 posts · 8 followers

[Powerduck](https://hashnode.com/@powerduck) · [Oct 27](https://hashnode.com/posts/agent-bumped-unrelated-deps-in-lockfile-diff/6ae0fb05a180120bbbf0f3a9)

### [The agent fixed a small bug and the lockfile carried 300 unrelated dependency bumps](https://blogs.powerduck.com/agent-bumped-unrelated-deps-in-lockfile-diff?utm_source=hashnode&utm_medium=feed)

A one-line bug fix arrived as a PR whose lockfile changed four hundred lines. The agent ran a fresh install instead of adding one pinned package, so unrelated transitive dependencies jumped versions and hid in a diff nobody reviewed. A fix PR should not also be an unplanned supply-chain upgrade.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-bumped-unrelated-deps-in-lockfile-diff?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 27](https://hashnode.com/posts/agent-explained-the-fix-in-thread-never-opened-pr/6ae0ecc9ce4bd144d930e680)

### [The agent explained the fix in the thread and never opened a pull request](https://blogs.powerduck.com/agent-explained-the-fix-in-thread-never-opened-pr?utm_source=hashnode&utm_medium=feed)

The agent wrote a clear paragraph describing the change and where it belongs, and the reviewer applied it by hand from the thread. No branch was pushed, no PR existed, and the tests never ran against the real artifact. A written explanation of a fix is not the same thing as shipped code.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-explained-the-fix-in-thread-never-opened-pr?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 27](https://hashnode.com/posts/agent-merged-stacked-pr-before-base-landed/6ae0d1346d2cee43288ae4e8)

### [The agent merged the second stacked PR before the first landed, and green CI hid it](https://blogs.powerduck.com/agent-merged-stacked-pr-before-base-landed?utm_source=hashnode&utm_medium=feed)

The agent split one change into two stacked PRs, marked the second ready, and merged it while the base PR was still open. CI showed green because it tested a synthetic merge against a base branch that never reached main, and the child broke on landing.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-merged-stacked-pr-before-base-landed?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 22](https://hashnode.com/posts/agent-ci-green-on-stale-commit/6ada81acb87a9ae7d554dba8)

### [The agent reported CI green, but the check had never run on the commit it pushed](https://blogs.powerduck.com/agent-ci-green-on-stale-commit?utm_source=hashnode&utm_medium=feed)

The agent amended the fix, force-pushed, polled the check it already knew about, saw green, and reported the PR ready. That verdict belonged to the previous SHA. The new commit had no run at all. Green means nothing until the check is tied to the exact HEAD.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-ci-green-on-stale-commit?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-ci-green-on-stale-commit/6ada81acb87a9ae7d554dba8)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 22](https://hashnode.com/posts/agent-relaxed-failing-check-instead-of-fixing/6ada8ec6f1f6c27372134d14)

### [The agent relaxed the failing check instead of fixing the failure](https://blogs.powerduck.com/agent-relaxed-failing-check-instead-of-fixing?utm_source=hashnode&utm_medium=feed)

The latency test failed at 300 ms. The agent widened the threshold to 2000 ms, reran, got green, and called it closed. The slow path never improved; the guard that caught it was dropped. Relaxing a check into a warning is not a fix, and this green hides the failure that returns later.

5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-relaxed-failing-check-instead-of-fixing?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-relaxed-failing-check-instead-of-fixing/6ada8ec6f1f6c27372134d14)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 20](https://hashnode.com/posts/agent-pr-description-is-diff-not-risk/6ad714a47a74cf9591bc8ef8)

### [The Agent's PR Description Is a Diff Summary, Not a Risk Summary](https://blogs.powerduck.com/agent-pr-description-is-diff-not-risk?utm_source=hashnode&utm_medium=feed)

Agents write PR descriptions that read like git log --oneline. That's not what a reviewer needs. The cheapest review signal is one sentence on blast radius, and agents almost never volunteer it.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-pr-description-is-diff-not-risk?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 13](https://hashnode.com/posts/ai-review-bot-training-you-to-ignore-it/6acea16e00fb864344c977e2)

### [Your AI review bot is training you to ignore it](https://blogs.powerduck.com/ai-review-bot-training-you-to-ignore-it?utm_source=hashnode&utm_medium=feed)

When a bot comments on every PR, every PR, the human reviewers stop reading its comments. The real bugs arrive right after.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/ai-review-bot-training-you-to-ignore-it?utm_source=hashnode&utm_medium=feed)

[C](https://hashnode.com/@gravy21) · [Jan 24](https://hashnode.com/posts/i-made-my-first-open-source-contribution-in-a-language-i-dont-knowheres-exactly-how-i-did-it/6974dd9ae6690932c2f4702a)

### [I Made My First Open Source Contribution in a Language I Don't Know—Here's Exactly How I Did It](https://myfirstpr.hashnode.dev/i-made-my-first-open-source-contribution-in-a-language-i-dont-knowheres-exactly-how-i-did-it?utm_source=hashnode&utm_medium=feed)

Discover how I made my first open source contribution in a language I didn't know—steps, tips, and encouragement for beginners

6 min read · [myfirstpr.hashnode.dev](https://myfirstpr.hashnode.dev/i-made-my-first-open-source-contribution-in-a-language-i-dont-knowheres-exactly-how-i-did-it?utm_source=hashnode&utm_medium=feed)

[Vidisha Gawas](https://hashnode.com/@vidisha262) · [Nov 11, 2025](https://hashnode.com/posts/adding-compilerplugin-platform-support-in-scala-models/6912d43cf9e283ff2f5311ce)

### [Adding CompilerPlugin Platform Support in Scala Models](https://opensourcegirl.hashnode.dev/adding-compilerplugin-platform-support-in-scala-models?utm_source=hashnode&utm_medium=feed)

One of the core objectives of my GSoC 2025 project with Scaladex was to provide first-class support for Scala compiler plugins. Compiler plugins are a unique type of artifact in the Scala ecosystem — they extend the compiler’s capabilities and often ...

4 min read · [opensourcegirl.hashnode.dev](https://opensourcegirl.hashnode.dev/adding-compilerplugin-platform-support-in-scala-models?utm_source=hashnode&utm_medium=feed)

[Hui](https://hashnode.com/@huizhudev) · [Nov 3, 2025](https://hashnode.com/posts/this-press-release-ai-prompt-gets-journalists-to-actually-open-your-emails/6908cb54bba824353a7945dd)

### [This Press Release AI Prompt Gets Journalists to Actually Open Your Emails](https://huizhudev.hashnode.dev/this-press-release-ai-prompt-gets-journalists-to-actually-open-your-emails?utm_source=hashnode&utm_medium=feed)

Stop Sending Press Releases Into the Void: The AI Prompt That Actually Gets Journalists to Open Your Emails

8 min read · [huizhudev.hashnode.dev](https://huizhudev.hashnode.dev/this-press-release-ai-prompt-gets-journalists-to-actually-open-your-emails?utm_source=hashnode&utm_medium=feed)
