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 / upstr
I work in a large team where dozens for branches and commits get created
daily.
Sometimes (and seemingly at random), the pull-request I create on Github
get 'polluted' with other peoples branches and I have to recreate them.
What might have 20 commits and 10 files ends up with hundred of other
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 remo
On 2017-01-04, at 4:29 PM, AD S 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 ${projec
Hello,
it's a bit unclear what exactly you mean by “polluted”. Pull requests in
GitHub are nothing but branches in other the repo of someone else (a fork)
compared with a branch of the main project. If everyone is happy, the
maintainer pushes the Big Green Button (merge this PR), then GitHub
conve
