I know .gitignore works in one direction, but does it work in the reverse direction?











up vote
0
down vote

favorite












Trying to understand how .gitignore files work: do they just ignore files only when you push to a branch or do they also ignore the same files if they've been updated on master, and you want to pull those changes? I know it works in one direction: when I want to push to a remote branch, and I'm wondering if it works in the reverse direction: when I want to pull changes for a gitignore-d file from a remote branch.










share|improve this question


















  • 1




    So many duplicates and refs elsewhere stackoverflow.com/q/3001888/1531971 stackoverflow.com/q/11451535/1531971 help.github.com/articles/ignoring-files (Show what research you've done and then re-ask in the context of all the reference material available to you.)
    – jdv
    Nov 19 at 17:23















up vote
0
down vote

favorite












Trying to understand how .gitignore files work: do they just ignore files only when you push to a branch or do they also ignore the same files if they've been updated on master, and you want to pull those changes? I know it works in one direction: when I want to push to a remote branch, and I'm wondering if it works in the reverse direction: when I want to pull changes for a gitignore-d file from a remote branch.










share|improve this question


















  • 1




    So many duplicates and refs elsewhere stackoverflow.com/q/3001888/1531971 stackoverflow.com/q/11451535/1531971 help.github.com/articles/ignoring-files (Show what research you've done and then re-ask in the context of all the reference material available to you.)
    – jdv
    Nov 19 at 17:23













up vote
0
down vote

favorite









up vote
0
down vote

favorite











Trying to understand how .gitignore files work: do they just ignore files only when you push to a branch or do they also ignore the same files if they've been updated on master, and you want to pull those changes? I know it works in one direction: when I want to push to a remote branch, and I'm wondering if it works in the reverse direction: when I want to pull changes for a gitignore-d file from a remote branch.










share|improve this question













Trying to understand how .gitignore files work: do they just ignore files only when you push to a branch or do they also ignore the same files if they've been updated on master, and you want to pull those changes? I know it works in one direction: when I want to push to a remote branch, and I'm wondering if it works in the reverse direction: when I want to pull changes for a gitignore-d file from a remote branch.







git






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 at 16:22









Sharon Kim

42




42








  • 1




    So many duplicates and refs elsewhere stackoverflow.com/q/3001888/1531971 stackoverflow.com/q/11451535/1531971 help.github.com/articles/ignoring-files (Show what research you've done and then re-ask in the context of all the reference material available to you.)
    – jdv
    Nov 19 at 17:23














  • 1




    So many duplicates and refs elsewhere stackoverflow.com/q/3001888/1531971 stackoverflow.com/q/11451535/1531971 help.github.com/articles/ignoring-files (Show what research you've done and then re-ask in the context of all the reference material available to you.)
    – jdv
    Nov 19 at 17:23








1




1




So many duplicates and refs elsewhere stackoverflow.com/q/3001888/1531971 stackoverflow.com/q/11451535/1531971 help.github.com/articles/ignoring-files (Show what research you've done and then re-ask in the context of all the reference material available to you.)
– jdv
Nov 19 at 17:23




So many duplicates and refs elsewhere stackoverflow.com/q/3001888/1531971 stackoverflow.com/q/11451535/1531971 help.github.com/articles/ignoring-files (Show what research you've done and then re-ask in the context of all the reference material available to you.)
– jdv
Nov 19 at 17:23












1 Answer
1






active

oldest

votes

















up vote
2
down vote













That's not how .gitignore works. The only job of the .gitignore file is to prevent you from adding them to the staging area. Thus, if you try to



git add file.txt


and file.txt is mentioned in the .gitignore file, you will get an error:



The following paths are ignored by one of your .gitignore files:
file.txt
Use -f if you really want to add them.


You can use the -f flag, as mentioned in the error message, to add the file anyways:



git add -f file.txt


This also implies that files that are already tracked by Git are not influenced by the .gitignore file anymore. More on that here: How to make Git "forget" about a file that was tracked but is now in .gitignore?






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',
    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%2f53378806%2fi-know-gitignore-works-in-one-direction-but-does-it-work-in-the-reverse-direct%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








    up vote
    2
    down vote













    That's not how .gitignore works. The only job of the .gitignore file is to prevent you from adding them to the staging area. Thus, if you try to



    git add file.txt


    and file.txt is mentioned in the .gitignore file, you will get an error:



    The following paths are ignored by one of your .gitignore files:
    file.txt
    Use -f if you really want to add them.


    You can use the -f flag, as mentioned in the error message, to add the file anyways:



    git add -f file.txt


    This also implies that files that are already tracked by Git are not influenced by the .gitignore file anymore. More on that here: How to make Git "forget" about a file that was tracked but is now in .gitignore?






    share|improve this answer

























      up vote
      2
      down vote













      That's not how .gitignore works. The only job of the .gitignore file is to prevent you from adding them to the staging area. Thus, if you try to



      git add file.txt


      and file.txt is mentioned in the .gitignore file, you will get an error:



      The following paths are ignored by one of your .gitignore files:
      file.txt
      Use -f if you really want to add them.


      You can use the -f flag, as mentioned in the error message, to add the file anyways:



      git add -f file.txt


      This also implies that files that are already tracked by Git are not influenced by the .gitignore file anymore. More on that here: How to make Git "forget" about a file that was tracked but is now in .gitignore?






      share|improve this answer























        up vote
        2
        down vote










        up vote
        2
        down vote









        That's not how .gitignore works. The only job of the .gitignore file is to prevent you from adding them to the staging area. Thus, if you try to



        git add file.txt


        and file.txt is mentioned in the .gitignore file, you will get an error:



        The following paths are ignored by one of your .gitignore files:
        file.txt
        Use -f if you really want to add them.


        You can use the -f flag, as mentioned in the error message, to add the file anyways:



        git add -f file.txt


        This also implies that files that are already tracked by Git are not influenced by the .gitignore file anymore. More on that here: How to make Git "forget" about a file that was tracked but is now in .gitignore?






        share|improve this answer












        That's not how .gitignore works. The only job of the .gitignore file is to prevent you from adding them to the staging area. Thus, if you try to



        git add file.txt


        and file.txt is mentioned in the .gitignore file, you will get an error:



        The following paths are ignored by one of your .gitignore files:
        file.txt
        Use -f if you really want to add them.


        You can use the -f flag, as mentioned in the error message, to add the file anyways:



        git add -f file.txt


        This also implies that files that are already tracked by Git are not influenced by the .gitignore file anymore. More on that here: How to make Git "forget" about a file that was tracked but is now in .gitignore?







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 19 at 16:40









        alfunx

        842313




        842313






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53378806%2fi-know-gitignore-works-in-one-direction-but-does-it-work-in-the-reverse-direct%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