Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow more flexible ignores (e.g. **/<file> for nested files) #41

Open
mcandre opened this issue Nov 6, 2013 · 3 comments
Open

Allow more flexible ignores (e.g. **/<file> for nested files) #41

mcandre opened this issue Nov 6, 2013 · 3 comments
Assignees

Comments

@mcandre
Copy link

mcandre commented Nov 6, 2013

I have several nested directories that I would like to churn all at once. Many of these each contain their own .gitignore, and I would like to configure churn to not only ignore the top level .gitignore, but any .gitignore in the sub directories as well.

Maybe my syntax is wrong?

$ churn -i ".gitignore, **/.gitignore"
...
| haskell/.gitignore        | 3             |
| latex/.gitignore          | 3             |
@danmayer
Copy link
Owner

danmayer commented Nov 8, 2013

makes sense, I will look at improving the matcher or get back to you with better syntax suggestions.

I basically would want to support the same style as gitignore files

@ghost ghost assigned danmayer Nov 8, 2013
@mcandre
Copy link
Author

mcandre commented Nov 8, 2013

@danmayer Yeah, I love gitignore style!

@danmayer
Copy link
Owner

danmayer commented Apr 4, 2014

Sorry so I basically forgot about this PR because I was looking for a gitingore implementation... Which was harder to come by than I thought... I tried a few approaches and backed out...

Eventually I pushed this

a06eaa5

which basically allows regex opposed to exact match.

I did see this which would implement a subset of the most important .gitignore rules... For now it seems to complicated

https://gist.github.com/MrJoy/3868993

@mcandre what do you think... would the regex version work well enough? Also, really sorry this fell off my radar.

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

No branches or pull requests

2 participants