我如何处理Git仓库中的图像？ [英] How do I handle images in a Git repo?

问题描述

我继承了一个中等大小的iOS项目 - 大约30,000行代码 - 它拥有疯狂的数量的图片资源。当然，我们使用Git / Github来scm。目前，这些图像被包含在目录树中，因此被吸收到回购站中，从而使得开发成为一件非常头疼的事情。

我们在项目中有4个开发者，一些是虚拟的。我发现将图像移动到Dropbox，从iOS项目中引用它们，并保持东西的形状。

有没有人对此想法发表评论？你在做什么处理图像/视频/音频文件在Git scm设置？ 解决方案

我会很紧张关于这一点，实际上;如果你想更新图像，然后改变主意？或者如果您需要使用旧图像构建维护版本？

如果这确实是一个问题 - 我从来没有看到这实际上是实践中的问题，但我会接受你的说法 - 为什么不仅仅为图像使用一个回购协议，还有其他所有协议？那么你可以懒得去同步图像。

I have inherited a medium sized iOS project - ~30,000 lines of code - that has an insane number of image assets. Of course we use Git/Github to scm. Currently the images are included in the directory tree and thus gets ingested into the repo, bloating the heck out of it and generally making development a big headache.

We have 4 devs on the project, some virtual. It occurs to me to move the images to Dropbox, refer to them from the iOS project and keep things ship shape.

Does anyone have a comment on this idea? What do you do do deal with image/video/audio files in a Git scm setup?

解决方案

I'd be pretty nervous about that, actually; what if you want to update an image, then change your mind? Or what if you need to build a maintenance release with old images?

If this is really a problem -- and I've never seen this actually be a problem in practice, but I'll take your word for it -- why not just use one repo for the images, another for everything else? You can then just be lazy about syncing the image one.

这篇关于我如何处理Git仓库中的图像？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！