Git push weird behavior
up vote
-2
down vote
favorite
I am working on a branch called sofian/issue_533. I simply want to add the changes to the branch on git and somehow I can't.
Here is a picture of what git is showing ...
Thanks for the help !
git github push pull
add a comment |
up vote
-2
down vote
favorite
I am working on a branch called sofian/issue_533. I simply want to add the changes to the branch on git and somehow I can't.
Here is a picture of what git is showing ...
Thanks for the help !
git github push pull
2
Possible duplicate of Cannot push to GitHub - keeps saying need merge
– cassandrad
Sep 20 at 16:11
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
I am working on a branch called sofian/issue_533. I simply want to add the changes to the branch on git and somehow I can't.
Here is a picture of what git is showing ...
Thanks for the help !
git github push pull
I am working on a branch called sofian/issue_533. I simply want to add the changes to the branch on git and somehow I can't.
Here is a picture of what git is showing ...
Thanks for the help !
git github push pull
git github push pull
edited Nov 11 at 16:30
Andy♦
30k20101158
30k20101158
asked Sep 20 at 15:59
Sox -
13013
13013
2
Possible duplicate of Cannot push to GitHub - keeps saying need merge
– cassandrad
Sep 20 at 16:11
add a comment |
2
Possible duplicate of Cannot push to GitHub - keeps saying need merge
– cassandrad
Sep 20 at 16:11
2
2
Possible duplicate of Cannot push to GitHub - keeps saying need merge
– cassandrad
Sep 20 at 16:11
Possible duplicate of Cannot push to GitHub - keeps saying need merge
– cassandrad
Sep 20 at 16:11
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
You need to pull from the remote source first, your local branch is not up-to-date. Look in the logs, git tries to hint at it.
And also, beware of git push
without any parameters, depending on your config, it might try to push all your local branches to their remote counterparts, which can be very unwanted. git push origin HEAD
is safer.
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
You need to pull from the remote source first, your local branch is not up-to-date. Look in the logs, git tries to hint at it.
And also, beware of git push
without any parameters, depending on your config, it might try to push all your local branches to their remote counterparts, which can be very unwanted. git push origin HEAD
is safer.
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
add a comment |
up vote
3
down vote
accepted
You need to pull from the remote source first, your local branch is not up-to-date. Look in the logs, git tries to hint at it.
And also, beware of git push
without any parameters, depending on your config, it might try to push all your local branches to their remote counterparts, which can be very unwanted. git push origin HEAD
is safer.
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
You need to pull from the remote source first, your local branch is not up-to-date. Look in the logs, git tries to hint at it.
And also, beware of git push
without any parameters, depending on your config, it might try to push all your local branches to their remote counterparts, which can be very unwanted. git push origin HEAD
is safer.
You need to pull from the remote source first, your local branch is not up-to-date. Look in the logs, git tries to hint at it.
And also, beware of git push
without any parameters, depending on your config, it might try to push all your local branches to their remote counterparts, which can be very unwanted. git push origin HEAD
is safer.
answered Sep 20 at 16:01
RomainValeri
1,24311124
1,24311124
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
add a comment |
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
Did not need to pull anything as Git said, the problem was the git push command. Thanks !
– Sox -
Sep 20 at 17:00
add a comment |
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%2fstackoverflow.com%2fquestions%2f52429037%2fgit-push-weird-behavior%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
2
Possible duplicate of Cannot push to GitHub - keeps saying need merge
– cassandrad
Sep 20 at 16:11