Thanks! That makes sense. On Thursday, January 5, 2017 at 10:58:43 PM UTC+10, Philip Oakley wrote: > > AD, > As Gergely noted, the Github PRS are branch references. > > It can be note that one can update a PR by force pushing an updated branch > to the website. I use this for revised versions of proposed updates to > Git-for-Windows, allowing me to rebase my branch and add in corrections. > This hints at the likely issue. > > I assume you (or team personnel) have not done any force pushes of the > branches they submitted, so the problem is on the flip side of the coin - > the destination branch(es) has moved. > > That is, the problem is that the branch you wanted to your submission to > be included in has moved (in some way, equivalent to a forced push) > > You say that there is a standard script that pushes to the test-branch > (from everybody). It is likely to be somewhere here that is the issue. > Those intermediate branches have been 'moved' in between the setup and > checking of the PR status. > > Philip. > > > On Thursday, January 5, 2017 at 7:37:30 AM UTC, Gergely Polonkai wrote: > >> 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 >> conveniently merges those two branches together. >> >> The only way I can think of getting “polluted” is when the main project >> accepts PRs often. This way your target branch quickly moves away from the >> state the PR was based on, and the author of the PR has to either recreate >> the PR or rebase their branch to the new state of the target (GitHub will >> recognise such rebase, and automatically updates the PR). If this is your >> case, unfortunately I can't see any other solutions. Maybe you should open >> a support case with GitHub. >> >> Best, >> Gergely >> >> On Thu, Jan 5, 2017, 01:22 AD S <ad...@radianweb.com.au> wrote: >> >>> 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 >>> peoples commits and thousands for files. >>> >>> It can be solved by creating a new pull request on that branch, but I >>> was curious as to why this occurs. >>> >>> Cheers >>> >>> >>> -- >>> 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+...@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.
