Hi,

most likely someone pushed develop before you and therefore you need to
pull (or pull --rebase depending on how your team works) to then be able to
push.
An other possibility is that you rebased some already pushed commits of
develop.

I hope it helps, let me know if you need anything.

Cheers

Ghislain

On 24 August 2016 at 00:56, <alexisdroid...@gmail.com> wrote:

> I am getting this strange ![rejected]  branch->branch (fetch first) error
> during git push. The push itself works just fine however, this error is
> creating a lot of confusion. I am a basic user of push and not very
> knowledgeable about the HEAD concept. Can someone explain what is going on?
> Thanks.,
>
> $git push
> Counting objects: 1358, done.
> Compressing objects: 100% (225/225), done.
> Writing objects: 100% (842/842), 129.49 KiB | 0 bytes/s, done.
> Total 842 (delta 684), reused 762 (delta 614)
>
> To repo@10.0.0.1:/repo/data/tests.git
>    9d7e36a..79da402  develop -> develop
>  ! [rejected]        develop -> develop (fetch first)
>
> error: failed to push some refs to 'repo@10.0.0.1:/repo/data/tests.git'
>
> hint: Updates were rejected because the remote contains work that you do
> hint: not have locally. This is usually caused by another repository
> pushing
> hint: to the same ref. You may want to first merge the remote changes
> (e.g.,
> hint: 'git pull') before pushing again.
> hint: See the 'Note about fast-forwards' in 'git push --help' for details.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to