How to push a new branch to remote git with commit message

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












My remote git server does not allow me to push anything without having a commit message.
Now i want to convert my perforce code to git using git p4 and push the converted code as a new branch to my remote git server. When i do git push origin mybranch it is failing as there is not commit that i did using git commit -a or git commit -m . How i can achieve this ?










share|improve this question



























    up vote
    1
    down vote

    favorite
    1












    My remote git server does not allow me to push anything without having a commit message.
    Now i want to convert my perforce code to git using git p4 and push the converted code as a new branch to my remote git server. When i do git push origin mybranch it is failing as there is not commit that i did using git commit -a or git commit -m . How i can achieve this ?










    share|improve this question

























      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      My remote git server does not allow me to push anything without having a commit message.
      Now i want to convert my perforce code to git using git p4 and push the converted code as a new branch to my remote git server. When i do git push origin mybranch it is failing as there is not commit that i did using git commit -a or git commit -m . How i can achieve this ?










      share|improve this question















      My remote git server does not allow me to push anything without having a commit message.
      Now i want to convert my perforce code to git using git p4 and push the converted code as a new branch to my remote git server. When i do git push origin mybranch it is failing as there is not commit that i did using git commit -a or git commit -m . How i can achieve this ?







      git github






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 25 at 14:41









      Rui F Ribeiro

      38.3k1476127




      38.3k1476127










      asked Jul 30 '15 at 13:49









      Niraj

      146113




      146113




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          You could add (or update) a README file in your new branch, then commit with a comment. At that point, you should be able to push the new branch. Providing some detail in the README about the origin of the code (in P4) may be useful if future pulls/pushes/merges to/from the external repo are needed.






          share|improve this answer




















            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            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: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2funix.stackexchange.com%2fquestions%2f219252%2fhow-to-push-a-new-branch-to-remote-git-with-commit-message%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
            0
            down vote













            You could add (or update) a README file in your new branch, then commit with a comment. At that point, you should be able to push the new branch. Providing some detail in the README about the origin of the code (in P4) may be useful if future pulls/pushes/merges to/from the external repo are needed.






            share|improve this answer
























              up vote
              0
              down vote













              You could add (or update) a README file in your new branch, then commit with a comment. At that point, you should be able to push the new branch. Providing some detail in the README about the origin of the code (in P4) may be useful if future pulls/pushes/merges to/from the external repo are needed.






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                You could add (or update) a README file in your new branch, then commit with a comment. At that point, you should be able to push the new branch. Providing some detail in the README about the origin of the code (in P4) may be useful if future pulls/pushes/merges to/from the external repo are needed.






                share|improve this answer












                You could add (or update) a README file in your new branch, then commit with a comment. At that point, you should be able to push the new branch. Providing some detail in the README about the origin of the code (in P4) may be useful if future pulls/pushes/merges to/from the external repo are needed.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jul 31 '15 at 15:15









                Andrew

                92557




                92557



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • 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%2funix.stackexchange.com%2fquestions%2f219252%2fhow-to-push-a-new-branch-to-remote-git-with-commit-message%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

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?