Skip to content

Standardize Handling of Conflicting Project Names to Local Platform Behavior #374

Description

@rjra2611
  • Project config corruption causes the CLI to lose track of the project cloud id and create a duplicate with project name 2

  • CLI Current Behavior:

    • on pull: Finds alternate name on conflict and pulls to the new directory. Also, updates the name in the cloud
    • on push: Renames locally on conflict/corruption and also renames in the cloud
  • Local Platform's current behavior

    • on pull: Fail and warn on conflict
    • on push: does not have any native logic for this case but maybe can be the same as pul i.e fail

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions