ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
pulling garbage revisions from github (Bug #527)
GitHub Merge Button commit:d64b022f
- github merge button leaves extra clutter "heads"
- pulling garbage revisions from github
$ git remote -v chili git://github.com/chiliproject/chiliproject.git (fetch) chili git://github.com/chiliproject/chiliproject.git (push) $ git ls-remote chili dd6d9d1c680f1bd0026372c39a685b6c6070fa0b HEAD dd6d9d1c680f1bd0026372c39a685b6c6070fa0b refs/heads/master effcd726a39b28f3dea5fca63aa6c5f7d4635c5f refs/heads/stable ddeb1a2a0f10db7e37f7bbdadbd22a194a589320 refs/heads/unstable b576ace2cad8510ad20b89103bb999b6b34e9f68 refs/pull/1/head 271aafc001e106845a5a2fcb45c5461fdaae6136 refs/pull/10/head f502ea16887296cf1735d498872ed08488122260 refs/pull/11/head 4dffc45ee96d0fe893264db56aa1a3ba14b0cfb8 refs/pull/12/head d0591d46e8773e1a5ce88bf45cdf42a054976582 refs/pull/13/head da45dfcc72b5a4235e9c1edb8f62364f026dd068 refs/pull/14/head 530951dd43adf2475767e0135f0e8cce914692d8 refs/pull/15/head . . .
|related to Bug #675: ChiliProject.org - set up local clone to not be a --mirror||Open||2011-10-28|
We've already contacted github about the same problem, for example commit:5b7508baadfac2abc0148ac5cd3f1dd8309b1e71 shows up here, it shows up on github in chiliproject/chiliproject if you know the hash, it's part of pull request 82, but it doesn't show on any branch in our repo on github or here for that matter.
Github's answer was: "This is a side effect of how we store pull requests for public repo networks. Private repos handle them differently to avoid that exact problem. If you're using --mirror you'll want to prune out the pull request branches afterwards."
In other words, we can't use
git --mirror or anything related on github public repos without it being polluted by pull request branches, which sucks. Holger proposed a fix to that (use
git fetch --all --tags --prune instead), but I'm not sure if anyone's changed the cronjob already.
Felix SchÃ¤fer wrote:
I'm not sure if anyone's changed the cronjob already.
Nope. The repo would have to be re-created to purge the existing commits and to remove them from cp.o's database. Also note that
git fetch ... just pulls new changesets but doesn't touch existing commits in the repo.
I think, the more correct solution in the long run would be to only handle commits inside
refs/tags and ignore all the others. However from the top of my head I don't know how to do it. Would need to investigate...