|
From: Thorsten O. <ad...@th...> - 2018-02-24 00:27:19
|
On Freitag, 23. Februar 2018 23:45:02 CET Miro Kropáček wrote: > no more abusing of https://github.com/freemint/travis-pr and > https://github.com/freemint/freemint.github.io That was absolutely necessary, especially for freemint.github.io where the snapshots are pushed to, and which has already grown to more than 600MB when you clone it. The *.io areas are limited to 1GB IIRC. > The final burst of motivation was adding Bintray support to Travis Oh. I didn't notice yet. >The final burst of motivation was adding Bintray support to Travis, so >instead of this dark magic (hats off, Thorsten!) I could do just this. It was still a good experience ;) And it's still a bit more flexible, since the same script can be used for snapshots and releases. Also, it looks that this kind of REST API that bintray uses is quite common, so it can easily be adapted for other providers or tasks. >git history has to be totally rewritten, so if you have a branch/fork of your >own, you have to do a hard reset + rebase/cherry-pick I wouldn't do that if it can be avoided. Might be a bit annoying to have the Travis commits in the log, but better than resetting it to a completely new repo. If you look at the link at the top, you will see that is has already been forked 9 times. All these forks will be affected by this, too, and of course every repo that someone has cloned locally. That will be at least as much work that you did, for everybody who is affected, maybe even worse (eg. i will have to clean up at least 2 repos, the cloned originally freemint repo, and the clone of my fork). And not everybody might know what he is doing there (remember my first attempts with the PRs *cough*). Also, to be honest, i rather spend my time with developing than with managing the repos. >otherwise I'll do the git force-push sometime on Sunday. I would wait a few days more. SF still seems to have problems with their mailing lists, maybe the complaints just don't make it to the list. |