Gitlab External LFS handling
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=29967)
</details>
<!--IssueSummary end-->
### Problem to solve
Change the way Gitlab handles external LFS
### Further details
We have artifactory LFS feature where we link our LFS data so that it is not stored in Gitlab for the large repository. When we use Gitlab LFS the LFS files are download formate from UI. But when we switched to external LFS, we need to disable Gitlab LFS for the repo from UI as per doc
https://docs.gitlab.com/ee/workflow/lfs/manage_large_binaries_with_git_lfs.html#hosting-lfs-objects-externally
Post which the download option from UI downloads only pointer which gives broken LFS kind of feel ut still I can fetch the LFS using git lfs commands.
### Proposal
Gitlab has to come with a better way to handle External LFS than just pointer or disable the download option from UI which is pointless
.
issue