On 2017-01-04, at 4:29 PM, AD S <a...@radianweb.com.au> wrote:
> 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}
Am I missing something here? The first command only runs if it can push the
current project out to the remote; if so, then the second merge command is a
no-op. It's then pushing again to another branch (for testing), and then
checking out a different branch?
What is this sequence supposed to do?
---
Entertaining minecraft videos
http://YouTube.com/keybounce
--
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.
