cleanup (prune) old branches about sharetribe HOT 5 CLOSED

Yep. The Git Flow suggestion is very good. I'll update our structure to match that, and at the same time clean up some old stuff. I think it's good to keep this repo rather clean, but still I think it could be ok to publish some feature branches sometimes if in need to share that with other developers before finnished. (like "api" branch now) but then should be named with git flow logic "feature/api"

from sharetribe.

sure we can keep some feature branches we collaborate on in main repo, but i remember seeing something like gnomet_dev... this one sounded like fitting better your fork ;)

looks like you already have done some major pruning \o/

i guess you can close this issue after switching github base branch to develop?

from sharetribe.

Oh yea, I somehow skipped the suggestion of switching the default branch to develop. Yea, it would show the activity better, and could make sense. Do you know if that is a common practice? I've somehow thought that the master is usually the default choice representing the latest stable?

from sharetribe.

hmmmm... ok i guess makes sense to keep master as base branch, especially that it should always have CI status green :)

from sharetribe.

Yea, that might be good point too. When it does, we can add that Travis-CI widget on the page.. :)

from sharetribe.