Nibble 0.5.0
Changed
- Everything of Nibble’s now lives under
lib/nibble/, andapp/is yours. Your models, controllers, jobs and views sit where a Rails application puts them, with nothing of ours beside them, and your views are looked in before Nibble’s. Class names are unchanged. Upgrade: if you added files underapp/, they stay exactly where they are and keep working. If you had changed one of Nibble’s files in place — whichbin/rails nibble:checkreports — git will stop on it during the merge, because that file has moved. bin/rails nibble:checkno longer reports files you added under a directory Nibble also uses as edits to ours. It reports what you changed or deleted of Nibble’s, which is what an upgrade can actually stop on..github/is gone. Workflows and dependency updates of ours have no business running in your repository, against your budget, on rules you did not write — and a site is a clone, so the only way not to send them is not to have them.bin/ciruns every check Nibble runs on itself..github/is yours, empty or otherwise. Upgrade: taking this release deletes our copy from your tree. If you had put your own workflows there, git stops on the conflict — keep your side.
What’s new
site/test/is yours for your own tests, run bybin/ciand bybin/rails test site/test, with Nibble’stest_helperavailable. Nibble’s own tests stay intest/.- The README says how to send a change back rather than carry it, and states the ownership rule in one line.