-
Notifications
You must be signed in to change notification settings - Fork 31
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
Git Ignore #24
Comments
bug already opened here: https://rt.cpan.org/Ticket/Display.html?id=59647 my initial position would be to just add a .gitignore in .dzil/profiles/default/skel but since you guys keep requesting, i'm ok to merge what you'll come up with. i definitely do not think adding a new git::ignore plugin would be the right way, though - just enhance git::init. so here's the deal - submit a pull request implementing it, and i'll merge.
|
Also, my position is that editor backup files (like
But it needs at least a config option to turn it off, because I (and probably many others) already have a suitable |
After thinking about this more, and envisioning what the arguments will be about what the default .ignores should be etc, and the fact that it isn't too difficult for people to get full customization via their profile skeleton, I think I'm going to stick with that route for now. @jquelin I think I maybe agree with your initial position now, that is probably the best and most unix-like approach. |
I'd like to enable this plugin to create a default .gitignore file that will ignore things like My-Package-* so that it can auto-ignore these build directories and tarballs created by dzil.
It seems like more people would be having an issue with these directories/files when using git::check ?
I have 2 ideas for how to do it and was wondering which you would prefer/think is best.
One is just to add
ignore
config options to git::init, and have it default to My-Package-* with an override being possible with an emptyignore
line.The other is to make a new plugin Git::Ignore, that accepts the same ignore lines with the same defaults, and presumably you would include this before Git::Init.
Thoughts/suggestions? Thanks.
The text was updated successfully, but these errors were encountered: