Provide a way to configure QB to only process pull-requests that are destined for a specific branch.
When user submits a pull-request, they request it to be merged to a specific destination branch (which is indicated at top of pull-request page on GitHub; e.g. https://github.com/01org/libva-utils/pull/44). We want to be able to have QB only process pull-requests for, say, "master" branch and not feature branches.
Description
Provide a way to configure QB to only process pull-requests that are destined for a specific branch.
When user submits a pull-request, they request it to be merged to a specific destination branch (which is indicated at top of pull-request page on GitHub; e.g. https://github.com/01org/libva-utils/pull/44). We want to be able to have QB only process pull-requests for, say, "master" branch and not feature branches.
Consider this, for example, to handle pull-requests for feature branches:
1. GitHub project A has feature branch X
2. GitHub project B has feature branch X
3. Project B feature branch X depends on project A feature branch X
4. Project B feature branch X is not compatible with project A branch Master
5. Pull request in project B for feature branch X can't be compiled until project A feature branch X is compiled
6. But QB does not know which branch the pull request belongs to. So #5 cannot be achieved.
U. Artie Eoff[21/Jun/17 12:34 AM]
Consider this, for example, to handle pull-requests for feature branches:
1. GitHub project A has feature branch X
2. GitHub project B has feature branch X
3. Project B feature branch X depends on project A feature branch X
4. Project B feature branch X is not compatible with project A branch Master
5. Pull request in project B for feature branch X can't be compiled until project A feature branch X is compiled
6. But QB does not know which branch the pull request belongs to. So #5 cannot be achieved.
Improvement
Resolved
Major
GitHub Pull Requests for specific merge branch
1. GitHub project A has feature branch X
2. GitHub project B has feature branch X
3. Project B feature branch X depends on project A feature branch X
4. Project B feature branch X is not compatible with project A branch Master
5. Pull request in project B for feature branch X can't be compiled until project A feature branch X is compiled
6. But QB does not know which branch the pull request belongs to. So #5 cannot be achieved.