Open markhalliwell opened 10 years ago
Comparing these PRs:
dreditor/dreditor/chrome-autoload https://api.github.com/repos/dreditor/dreditor/pulls/140
@sun's sun/dreditor/smart-commits https://api.github.com/repos/dreditor/dreditor/pulls/146
Looks like we can just filter out the branches on whether any PRs match $pr['head']['repo']['owner']['login'] === 'dreditor'
and $pr['head']['ref'] === $branch['name']
.
Actually, we can just filter out PRs that aren't currently HEAD (1.x currently).
sigh
PRs have the auto-rebase by GH, so I'll have to go with my original idea.
Feature branches on dreditor/dreditor that also have PRs show up as "branches" in the autobuilds list. This can confuse users as to which one they should use.
Feature branches themselves have to be manually rebased. This causes the build to technically be behind
HEAD
. Whereas the PR build is usually at a "mergeable" state (auto-rebased by GH) until it actually really needs to be rebased again.