Skip to content

Creating an ideal CLI for clone and add to an existing project #7

@quinnwai

Description

@quinnwai

Description

  • How do we manage state for a project?
  • In existing g3t, we have used git but only for specific commands rather than in totality (pulling, resolving conflicts)
  • We need to identify the ideal state of pulling a project and pushing up new project data without the assumption that you have an up-to-date project.

Ideal Steps

  1. g3t clone: git clone-type UI to clone
    1. see below, maybe in file browser, maybe another app
    2. project IDs are unique (been patched out) -> need to double check
    3. Populates only metadata folders (and hidden dirs, .g3t and .git and config)
  2. g3t ls: list of files and status on which files you have downloaded
    1. Calls the new ES table created in bucket config refactor
    2. Describes files that have been localized vs not
    3. Currently g3t status does the opposite (follows git status and looks at local compared to remote)
    4. Longer versions accessible via -vvv flag
  3. g3t pull <file_selection>
    1. Need to be separate pulling from metadata vs from files
    2. Incremental pull of metadata exists(?) -> need to double check
    3. Conflict resolution
  4. adding files, committing, and pushing
Image

Misc Notes

  • Create a git server instead of gen3 submission
    • or a git client on our servers?
  • Setting up a gitlab referencing any ACC-created gitlab
  • pull requests to merge?

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