Reuse an open PR when updating a dependency instead of superseding it

Hi guys, I think that when there's a new bump release on a package that has an already opened PR, you can just upgrade that PR avoiding to open a new one. Let's see this history, that happened in just 3 days: Bump webpack from 4.1.1 to 4.6.0 https://github.com/chrvadala/react-svg-pan-zoom/pull/99 Superseded by https://github.com/chrvadala/react-svg-pan-zoom/pull/101 Bump webpack from 4.1.1 to 4.7.0 https://github.com/chrvadala/react-svg-pan-zoom/pull/101 Superseded by https://github.com/chrvadala/react-svg-pan-zoom/pull/106 Bump webpack from 4.1.1 to 4.8.1 https://github.com/chrvadala/react-svg-pan-zoom/pull/106

Comments (0)

No comments yet. Start the discussion.

Reuse an open PR when updating a dependency instead of superseding it

Tags

Related issues

[Meta] Feedback on granular control over Copilot changes

unexpected status 401 Unauthorized issue

[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb

[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s

Video stops playing after some minutes

[MODEL] Claude verbose code comments by default — ignores instructions to stop.

Scope Codex VS Code chats to the current workspace/project

Update on "Co-authored-by: Copilot" in commit messages

Reuse an open PR when updating a dependency instead of superseding it

Comments (0)