this post was submitted on 24 Jul 2024
17 points (100.0% liked)

Git

2882 readers
16 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

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. 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
 

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
[–] Limonene@lemmy.world 5 points 3 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.

[–] borf@lemmynsfw.com -1 points 3 months ago (1 children)

I'd rather just use SVGs for the icons.

[–] Windex007@lemmy.world 4 points 3 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.