Hi Philip,
I am using my company's propriety software that automatically runs a few
git commands one after the other (it's meant to be more thorougher). The
process it runs when pushing to remote repo (testing branch) is:
- git push ${project} ${current_branch_refspec} - Push branch to remote
- git merge ${current_branch_refspec} - Merging feature into testing
branch
- git push ${project} ${peer_testing_branch} - Pushing testing branch to
remote: ${project}
- git checkout ${branch} - Checking out feature branch: ${branch}
On Thursday, January 5, 2017 at 5:43:45 AM UTC+10, Philip Oakley wrote:
>
> Hi AD
>
> What commands are you using?
>
> In particular what what is your default push style. You may not actually
> be pushing the branch/commit you expect. There was a change not that long
> ago that reduced the number of branches being pushed (by default) e.g.
> 'simple' vs 'matching' / current / upstream etc.
>
> Also, have to confirmned that you have actually added and comitted those
> files locally (and have a sha1 for the commit).
>
> You should then be able to check that the server actually has that commit
> sha1.
>
> Philip
>
--
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.
