From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Jacob Keller'" <jacob.keller@gmail.com>, "'Anmol Sethi'" <me@anmol.io>
Cc: "'Git mailing list'" <git@vger.kernel.org>
Subject: RE: Add option to git to ignore binary files unless force added
Date: Thu, 17 May 2018 08:37:17 -0400 [thread overview]
Message-ID: <002a01d3eddb$cdd3d8f0$697b8ad0$@nexbridge.com> (raw)
In-Reply-To: <CA+P7+xqQZzTrm274rbbP_O85Y+YGZ4PQ8PMFJnJtKR4wR0AObQ@mail.gmail.com>
On May 16, 2018 11:18 PM, Jacob Keller
> On Wed, May 16, 2018 at 5:45 PM, Anmol Sethi <me@anmol.io> 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.
>
> 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
next prev parent reply other threads:[~2018-05-17 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 0:45 Add option to git to ignore binary files unless force added Anmol Sethi
2018-05-17 3:18 ` Jacob Keller
2018-05-17 12:37 ` Randall S. Becker [this message]
2018-05-18 11:31 ` Anmol Sethi
2018-05-18 15:37 ` Randall S. Becker
2018-05-18 11:31 ` Anmol Sethi
2018-05-18 18:09 ` Jacob Keller
2018-05-18 18:11 ` Anmol Sethi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002a01d3eddb$cdd3d8f0$697b8ad0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=me@anmol.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).