<!-- Instructions: Use this template for a proof of concept or when a deeper technical evaluation is required. Please weigh tech evaluation issues and follow the instructions below accordingly. --> ### Topic to Evaluate Customers may be using a non-GitLab solution to store Git LFS objects. For example, Artifactory supports this. - [their quick start guide](https://jfrog.com/knowledge-base/git-lfs-artifactory-quick-start-guide/) - [their detailed docs](https://www.jfrog.com/confluence/display/JFROG/Git+LFS+Repositories) It involves adding a `.lfsconfig` to the repo ``` [lfs] url = "https://lfsremote:8080/api/lfs/project" ``` This was raised in a support ticket. (GitLab team members read more in the [ticket](https://gitlab.zendesk.com/agent/tickets/193040) and [SF](https://gitlab.my.salesforce.com/0016100000ZxrqHAAR)) Customers seeking to simplify their environment may want to consolidate git-lfs into GitLab. Purpose of this issue is to assemble a procedure for achieving this. related: * https://gitlab.com/gitlab-org/gitlab/-/issues/29967 ### High level - create a feature branch on a client that has git-lfs installed and working - remove the `.lfsconfig` - push this to GitLab along with the LFS objects - merge to the main branch. It's not that different from pushing an existing repository hosted on GitLab server 'A' to GitLab server 'B'. ### Detail To follow. ### To do - LFS objects not currently on the main branch? - Other feature branches? A server hook to ensure `.lfsconfig` is not pushed? [Seems like it'd be an update hook rather than a pre-receive hook](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks#_server_side_hooks) ### Tasks to Evaluate <!-- Outline the tasks with issues that you need to evaluate as a part of the implementation issue --> - [ ] Determine feasibility of the feature - [ ] Create issue for implementation or update existing implementation issue description with implementation proposal - [ ] Set weight on implementation issue - [ ] If weight is greater than 5, break issue into smaller issues - [ ] Add task - [ ] Add task ### Risks and Implementation Considerations <!-- Identify any risks found in the research, whether this is performance, impacts to other functionality or other bugs -->