It is a mere historical curiosity at this point. It may be confusing to have code inside, which gives an illusion of working code.
README would also be updated to pronounce the obsolete status near the top.
I'd be all for that, though we currently use this repository to run our migrations.
we could create a new repo which could store our migrations and schema, and then remove all the code from this repo and use it for issues and basic docs explaining how all the repos work together?
👍 to extracting schema and migrations to a separate repository. travis-database?
Sounds good, though maybe travis-migrations is a bit more explicit? Alternatively travis-databass.
Love both names!
👍 for travis-databass
I created travis-migrations. When it's confirmed that it works (and the early indications are good), I'll remove the code here.
REMOVE ALL THE THINGS
Sadly, we still need to keep the code. 😦
Did it again. 8675d4
You forgot to remove the 'production' branch. That confused me for a while, thought this was a weird way to turn it closed source or something.
Just removed it!
Thanks for pointing this out :)