How to push a new branch to remote git with commit message
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
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
add a comment |
up vote
1
down vote
favorite
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
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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
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
git github
edited Nov 25 at 14:41
Rui F Ribeiro
38.3k1476127
38.3k1476127
asked Jul 30 '15 at 13:49
Niraj
146113
146113
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Jul 31 '15 at 15:15
Andrew
92557
92557
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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