6

I'm trying to add a git clean-filter in order to ignore outputs and execution_count from my IPython notebook files.

I've basically followed this article (based on this SO answer) and modified it slightly for my needs. Also, I'm on Windows so the part about making the python script executable isn't needed as far as I know (see Python FAQ).

I want to bundle that to my repository so that other contributors get it too. I've saved the ipynb_drop_output.py at the root of my repository and saved the gitconfig and gitattributes files at the same place so at the root I have:

.gitignore
.gitconfig
.gitattributes
ipynb_drop_output.py
MyNotebook.ipynb

In .gitattributes:

*.ipynb filter=clean_ipynb

In .gitconfig:

[filter "clean_ipynb"]
    clean = ipynb_drop_output.py
    smudge = cat

I've tested the code of my ipynb_drop_output manually and it works like a charm. Yet git diff still shows me execution_count and outputs that changed. It appears the script isn't running at all.

I'm thinking it might be because of the clean = ipynb_drop_output.py section, but I've tried every variation: not include the .py, include the full path "C...\ipynb_drop_output.py", with forward slashes too etc.

My second theory is that git is just not looking at the .gitconfig file but I'm unclear how to tell it to and/or how to check that it is actually looking at it. And I thought the point of git config --file .gitconfig filter.clean_ipynb.clean ipynb_drop_output was to do just this...

How can I make it work on Windows please?

Community
  • 1
  • 1
Julien Marrec
  • 11,605
  • 4
  • 46
  • 63
  • Shouldn't that be in `.git/config`, not `.gitconfig`? – AlBlue Jul 03 '15 at 11:51
  • The linked article seems to imply that it shouldn't if you want it to propagate to other users. you use `git config --file .gitconfig filter.clean_ipynb.clean ipynb_drop_output` and it creates it there. Otherwise you would use git config --local. See [here](http://stackoverflow.com/a/18330114/2543372) as well – Julien Marrec Jul 03 '15 at 12:00
  • The point is there are no tools that are going to look at `.gitconfig`. You can use `git config` to write a file anywhere you want; doesn't mean anything's going to read it. – AlBlue Jul 03 '15 at 12:01
  • I see your point. My ./.git/config file has [include] path = .gitconfig – Julien Marrec Jul 03 '15 at 12:07
  • Any chance you got this to work? – Jody Jul 20 '15 at 20:04
  • My issue was a typo's git config command. FWIW, I'm on windows and using git bash, so that may help. – Jody Jul 20 '15 at 20:16
  • Jody, I never got it to work the way I wanted, and I never figured what was the problem. I ended setting a global git filter and that worked nicely. – Julien Marrec Jul 20 '15 at 22:47

1 Answers1

3

Let's assume that you have your repository checked out under: ~/myrepo/.

You need to tell git where to find your repo-wide custom .gitconfig, that you want all your users to use. You do that by running:

cd ~/myrepo/
git config --local include.path ../.gitconfig

note ../, which is missing from your attempts to make this work, as .gitconfig and .git/config are not in the same directory. The layout of your ~/myrepo/ will have:

.git/config
.gitconfig
.gitattributes

You will need the last 2 files committed to your repo.

All your users will have to execute the git config command from above right after cloning your repo, to tell git to trust ~/myrepo/.gitconfig. It's not possible to do it on their behalf for security reasons.

Finally, the reason your manual incorrect configuration was silently failing, is because git has been designed this way, to allow for optional configuration files. So as of this writing if in your .git/config you have:

[include]
    path = ../.gitconfig

and ../.gitconfig is not there, git will silently skip over it. Therefore, if you typed a wrong path, it will skip over it.

There is a new development on this front, and the jury is still out. Hopefully there will be a way to diagnose such git issues in the future.

stason
  • 5,409
  • 4
  • 34
  • 48