Git

2904 readers

1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

Follow programming.dev rules
Be excellent to each other, no hostility towards users for any reason
No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago

MODERATORS

Ategon

canpolat

jnovinger

How do you feel about storing binary files with Git? (lemmy.ca)

submitted 4 months ago by [email protected] to c/git

14 comments fedilink hide all child comments

I think it's generally agreed upon that large files that change often do not belong while small files that never change are fine. But there's still a lot of middle ground where the answer is not so clear to me.

So what's your stance on this? Where do you draw the line?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 4 months ago (1 children)

hiss The point of source control is keeping a history of the code that produces binary artifacts. For convenience' sake or because of some wild project-specific constraints people can do all kinds of things but IMO binaries in source control are yucky yucky bad bad bad.

[–] [email protected] 5 points 4 months ago (1 children)

I agree that the repository should only contain source files, not the output of the build process. However, in some cases (like icon images) the source files may be binary. I think small binaries that are required to build and/or run the software, and that are not an output of any build process, do make sense to put in the repository.

[–] [email protected] -1 points 4 months ago (1 children)

I'd rather just use SVGs for the icons.

[–] [email protected] 4 points 4 months ago

That's not really responding to their point. Are you saying that there are no project resources that aren't (or couldn't be) encoded as text representation in any conceivable project that is stored in a git repo?

I agree with your general point. I'm just curious if you have some unique project pattern techniques that allow you to draw such a hard line so confidently.