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

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
Labels
No labels