Remove all code from this repository #1841

Closed
BanzaiMan opened this Issue Jan 8, 2014 · 13 comments

6 participants

@BanzaiMan
Travis CI member

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.

@roidrage
Travis CI member

I'd be all for that, though we currently use this repository to run our migrations.

@joshk
Travis CI member

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?

@henrikhodne
Travis CI member

👍 to extracting schema and migrations to a separate repository. travis-database?

@joshk
Travis CI member

SUPER 👍

@roidrage
Travis CI member

Sounds good, though maybe travis-migrations is a bit more explicit? Alternatively travis-databass.

@joshk
Travis CI member

Love both names!

@BanzaiMan
Travis CI member

travis-databass!

@simi

👍 for travis-databass

@BanzaiMan BanzaiMan was assigned Jan 23, 2014
@BanzaiMan
Travis CI member

I created travis-migrations. When it's confirmed that it works (and the early indications are good), I'll remove the code here.

@henrikhodne henrikhodne added a commit that referenced this issue Jan 23, 2014
@henrikhodne henrikhodne REMOVE ALL THE THINGS
Close #1841.
b09e9af
@henrikhodne henrikhodne added a commit that closed this issue Jan 24, 2014
@henrikhodne henrikhodne REMOVE ALL THE THINGS
Close #1841.
b09e9af
@BanzaiMan
Travis CI member

Sadly, we still need to keep the code. 😦

@BanzaiMan BanzaiMan reopened this Jan 29, 2014
@BanzaiMan
Travis CI member

Did it again. 8675d4

@BanzaiMan BanzaiMan closed this Feb 9, 2014
@dequis

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.

@joshk
Travis CI member

Just removed it!

Thanks for pointing this out :)

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