Why my .git is always bigger when I just write a few code?












0















This happen twice: I already erased my repo, because of a filesize too big (>100mb), then it always failed when get test in CI/CD GitLab.



So i create the new repo, ... and it happens again: when I check my folder size, the main problem is .git: I dont know what happen and I don't know the solution.

I just have 2 branch (master and develop), and several commits (because it is a new repo)



Then I keep searching the solution , with git command:



git gc --aggresive --prune=now 


but still .git pack so huge, so I really need your help to find this solution, because I don't want to erase my repo again and the problem came again
my new repo (so bigg)



gitlab repo information:
gitlab repo information



whatsize folder:
whatsize folder










share|improve this question

























  • Can you post your .gitignore please? And is snitch a binary file?

    – Abdelilah El Aissaoui
    Nov 22 '18 at 2:43













  • It seems there are binaries in snitch and vendor. If the binaries are added and committed, .git gets big as expected.

    – ElpieKay
    Nov 22 '18 at 3:31


















0















This happen twice: I already erased my repo, because of a filesize too big (>100mb), then it always failed when get test in CI/CD GitLab.



So i create the new repo, ... and it happens again: when I check my folder size, the main problem is .git: I dont know what happen and I don't know the solution.

I just have 2 branch (master and develop), and several commits (because it is a new repo)



Then I keep searching the solution , with git command:



git gc --aggresive --prune=now 


but still .git pack so huge, so I really need your help to find this solution, because I don't want to erase my repo again and the problem came again
my new repo (so bigg)



gitlab repo information:
gitlab repo information



whatsize folder:
whatsize folder










share|improve this question

























  • Can you post your .gitignore please? And is snitch a binary file?

    – Abdelilah El Aissaoui
    Nov 22 '18 at 2:43













  • It seems there are binaries in snitch and vendor. If the binaries are added and committed, .git gets big as expected.

    – ElpieKay
    Nov 22 '18 at 3:31
















0












0








0


1






This happen twice: I already erased my repo, because of a filesize too big (>100mb), then it always failed when get test in CI/CD GitLab.



So i create the new repo, ... and it happens again: when I check my folder size, the main problem is .git: I dont know what happen and I don't know the solution.

I just have 2 branch (master and develop), and several commits (because it is a new repo)



Then I keep searching the solution , with git command:



git gc --aggresive --prune=now 


but still .git pack so huge, so I really need your help to find this solution, because I don't want to erase my repo again and the problem came again
my new repo (so bigg)



gitlab repo information:
gitlab repo information



whatsize folder:
whatsize folder










share|improve this question
















This happen twice: I already erased my repo, because of a filesize too big (>100mb), then it always failed when get test in CI/CD GitLab.



So i create the new repo, ... and it happens again: when I check my folder size, the main problem is .git: I dont know what happen and I don't know the solution.

I just have 2 branch (master and develop), and several commits (because it is a new repo)



Then I keep searching the solution , with git command:



git gc --aggresive --prune=now 


but still .git pack so huge, so I really need your help to find this solution, because I don't want to erase my repo again and the problem came again
my new repo (so bigg)



gitlab repo information:
gitlab repo information



whatsize folder:
whatsize folder







git macos .git-folder






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 5:44









VonC

841k29426653212




841k29426653212










asked Nov 22 '18 at 2:27









agny rezaagny reza

114




114













  • Can you post your .gitignore please? And is snitch a binary file?

    – Abdelilah El Aissaoui
    Nov 22 '18 at 2:43













  • It seems there are binaries in snitch and vendor. If the binaries are added and committed, .git gets big as expected.

    – ElpieKay
    Nov 22 '18 at 3:31





















  • Can you post your .gitignore please? And is snitch a binary file?

    – Abdelilah El Aissaoui
    Nov 22 '18 at 2:43













  • It seems there are binaries in snitch and vendor. If the binaries are added and committed, .git gets big as expected.

    – ElpieKay
    Nov 22 '18 at 3:31



















Can you post your .gitignore please? And is snitch a binary file?

– Abdelilah El Aissaoui
Nov 22 '18 at 2:43







Can you post your .gitignore please? And is snitch a binary file?

– Abdelilah El Aissaoui
Nov 22 '18 at 2:43















It seems there are binaries in snitch and vendor. If the binaries are added and committed, .git gets big as expected.

– ElpieKay
Nov 22 '18 at 3:31







It seems there are binaries in snitch and vendor. If the binaries are added and committed, .git gets big as expected.

– ElpieKay
Nov 22 '18 at 3:31














1 Answer
1






active

oldest

votes


















1














As commented, make sure your .gitignore will ignore any generated binary.



Try first to remove anty big files from your past commits, with BFG Repo cleaner ( faster than the native git filter-branch)



java -jar bfg.jar --strip-blobs-bigger-than 2M some-big-repo.git


Only then you can apply git gc/repack/prune in order for the size to actually go down.



git gc
git repack -Ad # kills in-pack garbage
git prune # kills loose garbage





share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423065%2fwhy-my-git-is-always-bigger-when-i-just-write-a-few-code%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    As commented, make sure your .gitignore will ignore any generated binary.



    Try first to remove anty big files from your past commits, with BFG Repo cleaner ( faster than the native git filter-branch)



    java -jar bfg.jar --strip-blobs-bigger-than 2M some-big-repo.git


    Only then you can apply git gc/repack/prune in order for the size to actually go down.



    git gc
    git repack -Ad # kills in-pack garbage
    git prune # kills loose garbage





    share|improve this answer




























      1














      As commented, make sure your .gitignore will ignore any generated binary.



      Try first to remove anty big files from your past commits, with BFG Repo cleaner ( faster than the native git filter-branch)



      java -jar bfg.jar --strip-blobs-bigger-than 2M some-big-repo.git


      Only then you can apply git gc/repack/prune in order for the size to actually go down.



      git gc
      git repack -Ad # kills in-pack garbage
      git prune # kills loose garbage





      share|improve this answer


























        1












        1








        1







        As commented, make sure your .gitignore will ignore any generated binary.



        Try first to remove anty big files from your past commits, with BFG Repo cleaner ( faster than the native git filter-branch)



        java -jar bfg.jar --strip-blobs-bigger-than 2M some-big-repo.git


        Only then you can apply git gc/repack/prune in order for the size to actually go down.



        git gc
        git repack -Ad # kills in-pack garbage
        git prune # kills loose garbage





        share|improve this answer













        As commented, make sure your .gitignore will ignore any generated binary.



        Try first to remove anty big files from your past commits, with BFG Repo cleaner ( faster than the native git filter-branch)



        java -jar bfg.jar --strip-blobs-bigger-than 2M some-big-repo.git


        Only then you can apply git gc/repack/prune in order for the size to actually go down.



        git gc
        git repack -Ad # kills in-pack garbage
        git prune # kills loose garbage






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 22 '18 at 5:40









        VonCVonC

        841k29426653212




        841k29426653212
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423065%2fwhy-my-git-is-always-bigger-when-i-just-write-a-few-code%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            RAC Tourist Trophy