I think it’d be great to have an option to have git ignore binary files. My repositories are always source only, committing a binary is always a mistake. At the moment, I have to configure the .gitignore to ignore every binary file and that gets tedious. Having git ignore all binary files would be great.
This could be achieved via an option in .gitconfig or maybe a special line in .gitignore.
I just want to never accidentally commit a binary again.
--
Best,
Anmol
From: Jacob Keller <hidden> Date: 2018-05-17 03:18:34
On Wed, May 16, 2018 at 5:45 PM, Anmol Sethi [off-list ref] wrote:
I think it’d be great to have an option to have git ignore binary files. My repositories are always source only, committing a binary is always a mistake. At the moment, I have to configure the .gitignore to ignore every binary file and that gets tedious. Having git ignore all binary files would be great.
This could be achieved via an option in .gitconfig or maybe a special line in .gitignore.
I just want to never accidentally commit a binary again.
--
Best,
Anmol
From: Randall S. Becker <hidden> Date: 2018-05-17 12:37:30
On May 16, 2018 11:18 PM, Jacob Keller
On Wed, May 16, 2018 at 5:45 PM, Anmol Sethi [off-list ref] wrote:
quoted
I think it’d be great to have an option to have git ignore binary files. My
repositories are always source only, committing a binary is always a mistake.
At the moment, I have to configure the .gitignore to ignore every binary file
and that gets tedious. Having git ignore all binary files would be great.
quoted
This could be achieved via an option in .gitconfig or maybe a special line in
.gitignore.
quoted
I just want to never accidentally commit a binary again.
I believe you can do a couple things. There should be a hook which you can
modify to validate that there are no binary files on pre-commit[1], or pre-
push[2] to verify that you never push commits with binaries in them.
You could also implement the update hook on the server if you control it, to
allow it to block pushes which contain binary files.
What about configuring ${HOME}/.config/git/ignore instead (described at https://git-scm.com/docs/gitignore). Inside, put:
*.o
*.exe
*.bin
*.dat
Etc....
Cheers,
Randall
That works but most binaries do not have a file extension. Its just not standard on linux.
On May 17, 2018, at 8:37 AM, Randall S. Becker [off-list ref] wrote:
On May 16, 2018 11:18 PM, Jacob Keller
quoted
On Wed, May 16, 2018 at 5:45 PM, Anmol Sethi [off-list ref] wrote:
quoted
I think it’d be great to have an option to have git ignore binary files. My
repositories are always source only, committing a binary is always a mistake.
At the moment, I have to configure the .gitignore to ignore every binary file
and that gets tedious. Having git ignore all binary files would be great.
quoted
This could be achieved via an option in .gitconfig or maybe a special line in
.gitignore.
quoted
I just want to never accidentally commit a binary again.
I believe you can do a couple things. There should be a hook which you can
modify to validate that there are no binary files on pre-commit[1], or pre-
push[2] to verify that you never push commits with binaries in them.
You could also implement the update hook on the server if you control it, to
allow it to block pushes which contain binary files.
What about configuring ${HOME}/.config/git/ignore instead (described at https://git-scm.com/docs/gitignore). Inside, put:
*.o
*.exe
*.bin
*.dat
Etc....
Cheers,
Randall
This definitely works but it would be more clean to just have git ignore the binary files from the get go.
On May 16, 2018, at 11:18 PM, Jacob Keller [off-list ref] wrote:
On Wed, May 16, 2018 at 5:45 PM, Anmol Sethi [off-list ref] wrote:
quoted
I think it’d be great to have an option to have git ignore binary files. My repositories are always source only, committing a binary is always a mistake. At the moment, I have to configure the .gitignore to ignore every binary file and that gets tedious. Having git ignore all binary files would be great.
This could be achieved via an option in .gitconfig or maybe a special line in .gitignore.
I just want to never accidentally commit a binary again.
--
Best,
Anmol
From: Randall S. Becker <hidden> Date: 2018-05-18 15:38:06
On May 18, 2018 7:31 AM, Anmol Sethi [off-list ref]
That works but most binaries do not have a file extension. Its just not
standard on linux.
quoted
On May 17, 2018, at 8:37 AM, Randall S. Becker [off-list ref]
wrote:
quoted
On May 16, 2018 11:18 PM, Jacob Keller
quoted
On Wed, May 16, 2018 at 5:45 PM, Anmol Sethi [off-list ref] wrote:
quoted
I think it’d be great to have an option to have git ignore binary
files. My
repositories are always source only, committing a binary is always a
mistake.
quoted
quoted
At the moment, I have to configure the .gitignore to ignore every
binary file and that gets tedious. Having git ignore all binary files would be
great.
quoted
quoted
quoted
This could be achieved via an option in .gitconfig or maybe a
special line in
.gitignore.
quoted
I just want to never accidentally commit a binary again.
I believe you can do a couple things. There should be a hook which
you can modify to validate that there are no binary files on
pre-commit[1], or pre- push[2] to verify that you never push commits
with binaries in them.
quoted
quoted
You could also implement the update hook on the server if you control
it, to allow it to block pushes which contain binary files.
What about configuring ${HOME}/.config/git/ignore instead (described at
I have a similar problem on my platform, with a different solution. My builds involve GCC binaries, NonStop L-series binaries (x86), and a NonStop J-series binaries (itanium). To keep me sane, I have all build targets going to separate directories, like Build/GCC, Build/Lbin, Build/Jbin away from the sources. This allows me to ignore Build/ regardless of extension and also to build different targets without link collisions. This is similar to how Java works (a.k.a. bin/). Much more workable, IMHO, than trying to manage individual binaries name by name or even by extension. I also have a mix of jpg and UTF-16 HTML that would end up in false-positives on a pure binary match and I do want to manage those.
What helps me is that I do most of my work in ECLIPSE, so derived resources (objects, generated sources) get auto-ignored by EGit, if you can make your compiler arrange that - but that's an ECLIPSE thing not a file system thing.
Cheers,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
From: Jacob Keller <hidden> Date: 2018-05-18 18:10:06
On Fri, May 18, 2018 at 4:31 AM, Anmol Sethi [off-list ref] wrote:
This definitely works but it would be more clean to just have git ignore the binary files from the get go.
Sure it'd be more convenient for you. But there are loads of possible
combinations, and the idea of what constitutes unwanted files is
hugely variable to each user. We don't really want to end up
supporting a million different ways to do this, and the hooks
interface provides a reasonable method for rejecting commits with
unwanted contents.
Thanks,
Jake
How about a hook to ignore certain files? Then you could ignore based on the contents of the fail instead of just the extension. It’d be very flexible.
On May 18, 2018, at 2:09 PM, Jacob Keller [off-list ref] wrote:
On Fri, May 18, 2018 at 4:31 AM, Anmol Sethi [off-list ref] wrote:
quoted
This definitely works but it would be more clean to just have git ignore the binary files from the get go.
Sure it'd be more convenient for you. But there are loads of possible
combinations, and the idea of what constitutes unwanted files is
hugely variable to each user. We don't really want to end up
supporting a million different ways to do this, and the hooks
interface provides a reasonable method for rejecting commits with
unwanted contents.
Thanks,
Jake