Once a large binary file makes it into the main repository, the whole thing is shot. It's so simple, and it's an LFS dealbreaker. I still don't understand why SmartGit seems on some religious mission to NOT have this feature. To be completely honest, I ditched SmartGit for GitKraken, and it's only because of two minuses that I'm still seeing if SmartGit has become friendly to Git LFS, (1) GitKraken is not good for managing a lot of repositories (microservices) where SmartGit has a folder list, and (2) GitKraken's internal Git client requires dual authentication when using LFS. I've been through all menus many times, and I'm not seeing it. I can't for the life of me figure out why SmartGit believes that there's now a badge. I still don't see this working. So this is the repository in SmartGit with one unchanged LFS file. And it would take Syntevo a few hours to add, which makes it all the more puzzling that they're so apparently against it. Otherwise, it's gigabytes of spam in the regular repository, all committed by accident. Without this indicator, we're absolutely *forced* to not use SmartGit for a large project. I'm a big boy, and if you really are against it, just let me know, and we can plan accordingly. So it would be really super awesome to hear what SmartGit even thinks of this indicator. Not having this is a dealbreaker for using LFS with SmartGit, not just as some emotional rant, but that it's really 100% unsafe to use SmartGit on a large project.īut if they've turned down this request over and over for the last 5 years, it sounds like they have some antagonistic opinion towards it. I can see it has been requested for the last 5 years, which makes me really nervous. It would be great to hear from Syntevo whether they ever intend to add this feature. For an LFS user, the lack of this feature results in immediate harm to repositories, by inadvertently uploading large files that will never leave. A non-LFS user couldn't care less about this. * Don't judge importance by the number of upvotes. I'm seriously considering abandoning a year of commit history on one repository just to get these files out. Every time a 3rd party plugin is added to the project, it brings some new, exotic, large file-type that inadvertently gets into the non-LFS repository. I already have 5 repositories with huge, permanent non-LFS files. I'm forced to do all my LFS repositories through GitKraken over this single issue, because it's not safe to use SmartGit. * For an LFS user, this is basically a dealbreaker.
"Yes" and "No", then it doesn't jump out at you that you're about to make a big and permanent mistake. * The LFS indicator should be easily readable, so it's glaringly obvious whether a file is handled by LFS. Your brain will crap out, and you'll inadvertently put some new file type into the permanent non-LFS repository. Otherwise you can't tell the difference between a file that's modified and a file-type that's misconfigured, requiring you to always have to understand the LFS indicator relative to the tracking status, over and over for thousands of game-content files. * It should not only be for untracked files, it should be for all files, regardless of tracking status.
The only opportunity to realize that your LFS status is wrong is before the commit. * Not having an LFS indicator quickly results in wrong and permanent commits of huge files that should have gone into LFS. I created a separate thread, not knowing this one was here.
0 kommentar(er)
