Skip to content

Surprising behavior when running vendetta with no arguments #10

@peterbourgon

Description

@peterbourgon
  • Navigate to the root of some Go repository
  • Run vendetta

Expected behavior: some kind of usage text letting me know how to add, update, or remove specific dependencies.

Actual behavior: vendetta assumes that I want to vendor all un-vendored imports, and proceeds to clone several submodules and update my .gitmodules file.

Perhaps my expectations are misaligned, but I expected finer-grained control. For example, the current default behavior expressed as e.g. vendetta add all, and other options, like vendetta remove github.com/some/import and vendetta update github.com/other/package.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions