Skip to content

Make VS Code Workspace setup optional #55

@thatvideoshopguy

Description

@thatvideoshopguy

Summary

When dev-clone is executed, it calls mkproject, which in turn triggers the postmkproject hook from virtualenvwrapper. In the onboarding process it asks to set this file up.

This behaviour is undesirable for developers who do not use VS Code, as it litters the project's parent directory with unnecessary configuration files. I propose adding a new flag to the dev-clone script, such as --no-workspace, that skips the creation of this IDE-specific file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions