Skip to content

Conversation

@antonkomarev
Copy link
Contributor

@antonkomarev antonkomarev commented Jan 5, 2026

@BenMorel .DS_Store files usually added automatically by MacOS X. It's pretty usual to ignore them.

@BenMorel
Copy link
Member

BenMorel commented Jan 5, 2026

Hi, this is something that can be ignored globally on your machine with a local .gitignore file:

git config --global core.excludesFile ~/.gitignore

I'm doing the same for .idea (PhpStorm), and I want to avoid opening the pandora box of gitignoring every setup out there!

@antonkomarev
Copy link
Contributor Author

antonkomarev commented Jan 5, 2026

Yeah, me too, but a lot of people doesn't use global ignores. I think it's not big deal to add this, because it's not IDE related, but OS.

It's hard to maintain ignores of all IDEs, but not hard to add OS meta files.

@wmBolles
Copy link

Yeah, me too, but a lot of people doesn't use global ignores. I think it's not big deal to add this, because it's not IDE related, but OS.

It's hard to maintain ignores of all IDEs, but not hard to add OS meta files.

I don’t agree with you. You should add .DS_Store to .gitignore.
Even though it’s OS-related, committing it can cause several issues and potential security risks.

Relying on global ignores is unreliable because many developers don’t configure them.
Adding OS-generated metadata files to the repository is easy, consistent, and prevents unnecessary exposure.

@BenMorel
Copy link
Member

I don’t agree with you. You should add .DS_Store to .gitignore.

It's unclear from your message who you're replying to, as you quoted @antonkomarev's reply. But if I understand correctly, you agree with him?

I cannot find a general consensus on the matter. If you know a repo with an comprehensive list of files to ignore, we could set it up in every brick repo. If we're going to do this, it must at least be consistent across repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants