When viewing a commit on GitHub, there is a file listed with #--># appended to it (see picture). What does...












0















GitHub Arrow



I'm viewing the diffs introduced by a commit to a repository on GitHub, and one of the files has the file name with this mysterious (to me) string appended to it. The file name is gulpfile.js and it is followed by 100755 --> 100644. Does anyone know what it means?










share|improve this question



























    0















    GitHub Arrow



    I'm viewing the diffs introduced by a commit to a repository on GitHub, and one of the files has the file name with this mysterious (to me) string appended to it. The file name is gulpfile.js and it is followed by 100755 --> 100644. Does anyone know what it means?










    share|improve this question

























      0












      0








      0








      GitHub Arrow



      I'm viewing the diffs introduced by a commit to a repository on GitHub, and one of the files has the file name with this mysterious (to me) string appended to it. The file name is gulpfile.js and it is followed by 100755 --> 100644. Does anyone know what it means?










      share|improve this question














      GitHub Arrow



      I'm viewing the diffs introduced by a commit to a repository on GitHub, and one of the files has the file name with this mysterious (to me) string appended to it. The file name is gulpfile.js and it is followed by 100755 --> 100644. Does anyone know what it means?







      github






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 25 at 18:21









      helenhelen

      32




      32






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Basically this means that the commit removed the "executable" bit from the file, i.e. chmod -x was done by the commit author.





          The numbers are in the same format as st_mode in Unix stat().




          • The first 10 (octal) indicates a regular file. (04 is a directory, 12 is a symlink, 16 is a Git-specific value indicating a submodule.)


          • The next 0644 (octal) are the regular Unix permissions – the file is readable by everyone and writable by its owner. Compared to that, 0755 also means the file is executable by everyone.



          (Note that Git doesn't store the real permissions, only a look-alike: it always stores 0755 if the file is executable and 0644 if it is not, and 0000 for directories and other non-file objects.)



          You can see these values for local Git repositories by running git ls-tree <treeish>, e.g.:




          $ git ls-tree HEAD
          100644 blob e42c7ff372783714c873fb8f33c7c04fba1d7e02 Plain_file.txt
          040000 tree c909f07b68d787edabba4384f105fc37ed942e17 This_is_a_directory
          120000 blob ba6b7e01db412305ff893b6c1cf279094f5656ac Symlink_to_a_file.txt
          160000 commit 6a41d623cdd0f93f16dff679963d2a5b4f856bdb Some_submodule
          100755 blob fe7ce105da1306e8648d8e2849cc3c72ca512d20 An_executable_script.sh





          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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%2fsuperuser.com%2fquestions%2f1398509%2fwhen-viewing-a-commit-on-github-there-is-a-file-listed-with-appended-to-i%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









            0














            Basically this means that the commit removed the "executable" bit from the file, i.e. chmod -x was done by the commit author.





            The numbers are in the same format as st_mode in Unix stat().




            • The first 10 (octal) indicates a regular file. (04 is a directory, 12 is a symlink, 16 is a Git-specific value indicating a submodule.)


            • The next 0644 (octal) are the regular Unix permissions – the file is readable by everyone and writable by its owner. Compared to that, 0755 also means the file is executable by everyone.



            (Note that Git doesn't store the real permissions, only a look-alike: it always stores 0755 if the file is executable and 0644 if it is not, and 0000 for directories and other non-file objects.)



            You can see these values for local Git repositories by running git ls-tree <treeish>, e.g.:




            $ git ls-tree HEAD
            100644 blob e42c7ff372783714c873fb8f33c7c04fba1d7e02 Plain_file.txt
            040000 tree c909f07b68d787edabba4384f105fc37ed942e17 This_is_a_directory
            120000 blob ba6b7e01db412305ff893b6c1cf279094f5656ac Symlink_to_a_file.txt
            160000 commit 6a41d623cdd0f93f16dff679963d2a5b4f856bdb Some_submodule
            100755 blob fe7ce105da1306e8648d8e2849cc3c72ca512d20 An_executable_script.sh





            share|improve this answer




























              0














              Basically this means that the commit removed the "executable" bit from the file, i.e. chmod -x was done by the commit author.





              The numbers are in the same format as st_mode in Unix stat().




              • The first 10 (octal) indicates a regular file. (04 is a directory, 12 is a symlink, 16 is a Git-specific value indicating a submodule.)


              • The next 0644 (octal) are the regular Unix permissions – the file is readable by everyone and writable by its owner. Compared to that, 0755 also means the file is executable by everyone.



              (Note that Git doesn't store the real permissions, only a look-alike: it always stores 0755 if the file is executable and 0644 if it is not, and 0000 for directories and other non-file objects.)



              You can see these values for local Git repositories by running git ls-tree <treeish>, e.g.:




              $ git ls-tree HEAD
              100644 blob e42c7ff372783714c873fb8f33c7c04fba1d7e02 Plain_file.txt
              040000 tree c909f07b68d787edabba4384f105fc37ed942e17 This_is_a_directory
              120000 blob ba6b7e01db412305ff893b6c1cf279094f5656ac Symlink_to_a_file.txt
              160000 commit 6a41d623cdd0f93f16dff679963d2a5b4f856bdb Some_submodule
              100755 blob fe7ce105da1306e8648d8e2849cc3c72ca512d20 An_executable_script.sh





              share|improve this answer


























                0












                0








                0







                Basically this means that the commit removed the "executable" bit from the file, i.e. chmod -x was done by the commit author.





                The numbers are in the same format as st_mode in Unix stat().




                • The first 10 (octal) indicates a regular file. (04 is a directory, 12 is a symlink, 16 is a Git-specific value indicating a submodule.)


                • The next 0644 (octal) are the regular Unix permissions – the file is readable by everyone and writable by its owner. Compared to that, 0755 also means the file is executable by everyone.



                (Note that Git doesn't store the real permissions, only a look-alike: it always stores 0755 if the file is executable and 0644 if it is not, and 0000 for directories and other non-file objects.)



                You can see these values for local Git repositories by running git ls-tree <treeish>, e.g.:




                $ git ls-tree HEAD
                100644 blob e42c7ff372783714c873fb8f33c7c04fba1d7e02 Plain_file.txt
                040000 tree c909f07b68d787edabba4384f105fc37ed942e17 This_is_a_directory
                120000 blob ba6b7e01db412305ff893b6c1cf279094f5656ac Symlink_to_a_file.txt
                160000 commit 6a41d623cdd0f93f16dff679963d2a5b4f856bdb Some_submodule
                100755 blob fe7ce105da1306e8648d8e2849cc3c72ca512d20 An_executable_script.sh





                share|improve this answer













                Basically this means that the commit removed the "executable" bit from the file, i.e. chmod -x was done by the commit author.





                The numbers are in the same format as st_mode in Unix stat().




                • The first 10 (octal) indicates a regular file. (04 is a directory, 12 is a symlink, 16 is a Git-specific value indicating a submodule.)


                • The next 0644 (octal) are the regular Unix permissions – the file is readable by everyone and writable by its owner. Compared to that, 0755 also means the file is executable by everyone.



                (Note that Git doesn't store the real permissions, only a look-alike: it always stores 0755 if the file is executable and 0644 if it is not, and 0000 for directories and other non-file objects.)



                You can see these values for local Git repositories by running git ls-tree <treeish>, e.g.:




                $ git ls-tree HEAD
                100644 blob e42c7ff372783714c873fb8f33c7c04fba1d7e02 Plain_file.txt
                040000 tree c909f07b68d787edabba4384f105fc37ed942e17 This_is_a_directory
                120000 blob ba6b7e01db412305ff893b6c1cf279094f5656ac Symlink_to_a_file.txt
                160000 commit 6a41d623cdd0f93f16dff679963d2a5b4f856bdb Some_submodule
                100755 blob fe7ce105da1306e8648d8e2849cc3c72ca512d20 An_executable_script.sh






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 25 at 19:46









                grawitygrawity

                239k37506561




                239k37506561






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1398509%2fwhen-viewing-a-commit-on-github-there-is-a-file-listed-with-appended-to-i%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

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                    Eduardo VII do Reino Unido