XMLWordPrintable

Details

    Description

      I have logged this via email, and via an account linked to the repository in question too, but getting no response. I realise this may be due to it being a weird time and you may have no support engineers working (which is a tad disappointing for a paid service), but I have to work because I have to hit a release deadline for Monday! So I'm desperately trying to get help from wherever I can...

      The repository in question is https://bitbucket.org/odokoltd/unleashed - it has been running at over 1Gb for a week or so because I had to check in some binary files to satisfy a customer who uses the repository to get access to the materials we maintain for them.

      However, having completed writing some distribution scripts that negate the need for those files to be checked in to the repository, I started following the instructions from Option 1) below, in order to remove the offending large binaries and try and resolve the "over 1Gb" issue:

      https://confluence.atlassian.com/display/BITBUCKET/Maintaining+a+Git+Repository

      But far from resolving the issue, this seems to have pushed the repository from 1Gb to over 2Gb. WTF? And apparently this means the repository is now completely unuseable too! That's nothing short of disastrous, given it's how we maintain a client relationship...

      The local repository on my system is now just 300Mb. Is there a way I can get access back to our Bitbucket origin in order to push up my local git repo'? I 'think' if I am able to run git push --all --force all should be well. At least I hope, because I don't really understand how following YOUR instructions and trying to remove the large files has caused this issue in the first place!

      Attachments

        Activity

          People

            Unassigned Unassigned
            632f8e3c9741 glowkeeper
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: