Skip to content

Add "Prompt" option to "Run Pub Get on Pubspec Changes" #4110

Closed

Description

@rlipscombe

When I'm doing an interactive rebase (on Windows, if that makes a difference), and VS Code is open, changes to pubspec.yaml (as the commits are replayed) cause the VS Code extension to re-run pub get. This occasionally causes git to fail the rebase, because pubspec.lock has changed while it's attempting to replay the changes.

Ideally, the extension would hold off running pub get until the rebase had finished, but I have no idea how you'd do that.

As a compromise, it would be useful if the "Run Pub Get on Pubspec Changes" was changed from a boolean to a tri-state: "Always | Prompt | Never".

Activity

  1. added
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    on Aug 19, 2022
  2. DanTup commented on Aug 22, 2022

    @DanTup
    Member

    I think detecting an in-progress rebase (and then when it finishes) might be tricky (and/or unreliable), but I think having an option to always prompt is reasonable (we already have a prompt for when you open a project and we detect the files are out of sync).

  3. added this to the v3.48.0 milestone on Aug 22, 2022
  4. added
    in commandsRelates to commands (usually invoked from the command Palette)
    on Aug 22, 2022
  5. added a commit that references this issue on Sep 2, 2025
    029850e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    in commandsRelates to commands (usually invoked from the command Palette)is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions