Some contributions to FuelPHP are relatively easy and you can just tinker with that bit of code, then commit it.
But, if you're developing something that requires things like database access, how do you commit your changes without sending your test app to the repo? Do you just permanently have files rolling around that you never commit, or some other strategy?
It is the main reason (or at least of of the important ones) for using submodules and seperate repo's. So you can commit something to fuel/core without being worried about anything in app.
I do all my testing in a separate virtual host install, setup so I can easily switch core and package versions, and all test code is in a module called test. I've excluded this module in my .gitignore so it will never be part of a commit.
Donate
