Skip to content

Smart defaults for duplicate repo names #9

Open
@dylan-smith

Description

@dylan-smith

If duplicate repo names are detected, instead of just spitting out a warning and putting the onus on the user, maybe do something intelligent to ensure unique repo names, then the user can always changed the migration script if desired.

E.g. prefix with Team Project and/or Org name (if not already doing that), and/or toss a number on the end

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions