blocks|key|2765762|text|自2016-01-10起，这已被添加到gh搜索栏api中，请参阅下一答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2765763|原始接受(现已公布的答案)未编辑。|2765764|2765765|目前不能通过Web界面使用|2765766|GitHub目前不提供通过其web接口按其目标分支过滤pull-requests的方法。相反，您当前得到的只是带有主题分支名称的整个拉请求列表：|2765767|​|2765768|📷|atomic|offset|length|2765769|2765770|单击pull-request将显示目标分支，但这并不能真正帮助您完成您想要做的任何过滤。|2765771|您可以改用GitHub+REST+API|2765772|但是，可以使用GitHub+REST+API过滤pull-requests：|2765773|GET+/repos/:owner/:repo/pulls?base=:branch|code-block|syntax|javascript|2765774|这应该会向您显示所有打开的repo+:owner/:repo的拉取请求，这些请求通过以:branch为基础分支的请求进行过滤。从文档中：|style|CODE|2765775|2765776|筛选器按基本分支名称提取。示例：gh-pages。|blockquote|2765777|2765778|2765779|使用cURL的示例|2765780|如果您有可用的curl，您可以从命令行在公共存储库上对其进行测试。在这里，查询的存储库是这个(https://github.com/codecombat/codecombat)，我们从名为master的base分支(PR合并到的分支)获得所有拉请求，然后将结果存储到我们接下来将解析的pulls.json文件中。|BOLD|2765781|curl+https://api.github.com/repos/codecombat/codecombat/pulls?base=master+>+\
pulls.json|2765782|这将返回以下形式的JSON响应，该响应现在存储在文件pulls.json中。|2765783|[
++{
++++"url":+"https://api.github.com/repos/codecombat/codecombat/pulls/879",
++++"id":+14955421,
++++"html_url":+"https://github.com/codecombat/codecombat/pull/879",
++++"head":+{
++++++"label":+"DanielRodriguezRivero:patch-4",
++++++"ref":+"patch-4",
++++++"sha":+"baff84f0aeee12f23e3608558ae5341a0b5f939b",
++++++"repo":+{
++++++++"id":+16202384,
++++++++"name":+"codecombat",
++++++++"full_name":+"DanielRodriguezRivero/codecombat"
++++++}
++++},
++++"base":+{
++++++"label":+"codecombat:master",
++++++"ref":+"master",
++++++"sha":+"5e2f3ac7cb731a6e40e81737a5122c7fe1b746d3",
++++++"repo":+{
++++++++"id":+15193430,
++++++++"name":+"codecombat",
++++++++"full_name":+"codecombat/codecombat"
++++++}
++++}
++}
]|2765784|数组中的每个对象都是一个拉取请求(PR)，由base=target分支过滤，我们在上面的curl命令中将其指定为master。|2765785|JSON实际上包含的信息比这多得多；为了显示这个问题的相关部分，我删除了它的大部分内容。|2765786|解析cURL响应|2765787|您可能会编写一个Python/Ruby/PHP/任何脚本，然后解析出每个拉请求的html_url属性，并在命令行中列出它。例如，下面是一个简单的Ruby脚本，它将解析从curl输出中保存的JSON响应的输出：|2765788|require+'json'

json+=+JSON.parse(File.read('./pulls.json'))
pulls+=+json.map+{+%7Cpull%7C+{+title:+pull['title'],+url:+pull['html_url']+}+}

pulls.each+do+%7Cpull%7C
++puts+pull.values
++puts
end|2765789|它输出以下内容：|2765790|$+ruby+parser.rb
Update+es-ES.coffee
https://github.com/codecombat/codecombat/pull/879

Fix+deltas+referring+to+last+system+saved
https://github.com/codecombat/codecombat/pull/874

Refactor+getNameById+and+add+naming+to+systems+in+deltas
https://github.com/codecombat/codecombat/pull/866

Traducido+varios+textos+del+fichero+es-ES.coffe+al+espa├▒ol+de+Espa├▒a
https://github.com/codecombat/codecombat/pull/865

Anon+name+collide
https://github.com/codecombat/codecombat/pull/834|2765791|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/41e8fcb92df2673dac0174c02079ecd2.png|imageAlt|1|LINK|MUTABLE|url|https://developer.github.com/v3/pulls/#list-pull-requests|2|https://github.com/codecombat/codecombat^0|0|0|0|0|0|0|0|1|0|0|0|0|0|7|F|1|0|0|I|C|17|7|0|0|G|8|0|0|0|0|7|4|2M|6|2T|4|3Y|A|1B|14|2|0|0|Q|A|0|0|M|B|18|4|1K|6|0|0|0|14|8|2C|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2H|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|2J|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|2K|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|2L|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|2M|8|@]|9|@$N|2N|O|2O|1|2P]]|A|$]]|$1|P|3|J|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2R|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2S|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|2T|8|@]|9|@$N|2U|O|2V|1|2W]]|A|$]]|$1|W|3|X|5|Y|7|2X|8|@]|9|@]|A|$Z|10]]|$1|11|3|12|5|6|7|2Y|8|@$N|2Z|O|30|13|14]|$N|31|O|32|13|14]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|33|8|@]|9|@]|A|$]]|$1|16|3|17|5|18|7|34|8|@$N|35|O|36|13|14]]|9|@]|A|$]]|$1|19|3|-4|5|6|7|37|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|38|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|39|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3A|8|@$N|3B|O|3C|13|14]|$N|3D|O|3E|13|14]|$N|3F|O|3G|13|14]|$N|3H|O|3I|13|1F]]|9|@$N|3J|O|3K|1|3L]]|A|$]]|$1|1G|3|1H|5|Y|7|3M|8|@]|9|@]|A|$Z|10]]|$1|1I|3|1J|5|6|7|3N|8|@$N|3O|O|3P|13|1F]]|9|@]|A|$]]|$1|1K|3|1L|5|Y|7|3Q|8|@]|9|@]|A|$Z|10]]|$1|1M|3|1N|5|6|7|3R|8|@$N|3S|O|3T|13|14]|$N|3U|O|3V|13|14]|$N|3W|O|3X|13|14]]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|40|8|@$N|41|O|42|13|14]|$N|43|O|44|13|14]]|9|@]|A|$]]|$1|1U|3|1V|5|Y|7|45|8|@]|9|@]|A|$Z|10]]|$1|1W|3|1X|5|6|7|46|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|Y|7|47|8|@]|9|@]|A|$Z|10]]|$1|20|3|-4|5|6|7|48|8|@]|9|@]|A|$]]]|21|$22|$5|23|24|25|A|$26|27|28|-4]]|29|$5|2A|24|2B|A|$2C|2D]]|2E|$5|2A|24|2B|A|$2C|2F]]]]

As of 2016-01-10 this has been added to the gh search bar api, see next answer.
Original accepted (and now outed answer) left un-edited.
<hr />
<h2>Currently Not Available via Web Interface</h2>
GitHub currently does not provide a way to filter pull-requests by their target
branch through their web interface. Instead, all you currently get is just the
entire list of pull-requests with the names of the topic branches:
<a href="https://i.stack.imgur.com/DiHMq.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DiHMq.png" alt="GitHub Pull-Request UI" /></a>
Clicking into a pull-request will show the target branch, but that doesn't
really help you do any of the filtering that you want to do.
<h2>You Can Use the GitHub REST API Instead</h2>
It is possible to filter pull-requests by using the <a href="https://developer.github.com/v3/pulls/#list-pull-requests" rel="nofollow noreferrer">GitHub REST API</a>,
however:
<pre class="lang-none prettyprint-override"><code>GET /repos/:owner/:repo/pulls?base=:branch
</code></pre>
That should show you all the open pull-requests for the repo <code>:owner/:repo</code>,
filtered by requests that target <code>:branch</code> as their base branch. From the
documentation:
<blockquote>
Filter pulls by base branch name. Example: <code>gh-pages</code>.
</blockquote>
<h3>Example Using cURL</h3>
If you have <code>curl</code> available, you can test this on a public repo from the
command line. Here, the repo being queried is this one (<a href="https://github.com/codecombat/codecombat" rel="nofollow noreferrer">https://github.com/codecombat/codecombat</a>), and we are getting all pull requests from <code>base</code> branch (the branch the PRs are merging TO) named <code>master</code>, and then storing the results into a pulls.json file we will parse through next.

<pre><code>curl https://api.github.com/repos/codecombat/codecombat/pulls?base=master &gt; \
pulls.json
</code></pre>
That will return a JSON response of the following form, now stored inside file pulls.json:
<pre class="lang-javascript prettyprint-override"><code>[
 {
 &quot;url&quot;: &quot;https://api.github.com/repos/codecombat/codecombat/pulls/879&quot;,
 &quot;id&quot;: 14955421,
 &quot;html_url&quot;: &quot;https://github.com/codecombat/codecombat/pull/879&quot;,
 &quot;head&quot;: {
 &quot;label&quot;: &quot;DanielRodriguezRivero:patch-4&quot;,
 &quot;ref&quot;: &quot;patch-4&quot;,
 &quot;sha&quot;: &quot;baff84f0aeee12f23e3608558ae5341a0b5f939b&quot;,
 &quot;repo&quot;: {
 &quot;id&quot;: 16202384,
 &quot;name&quot;: &quot;codecombat&quot;,
 &quot;full_name&quot;: &quot;DanielRodriguezRivero/codecombat&quot;
 }
 },
 &quot;base&quot;: {
 &quot;label&quot;: &quot;codecombat:master&quot;,
 &quot;ref&quot;: &quot;master&quot;,
 &quot;sha&quot;: &quot;5e2f3ac7cb731a6e40e81737a5122c7fe1b746d3&quot;,
 &quot;repo&quot;: {
 &quot;id&quot;: 15193430,
 &quot;name&quot;: &quot;codecombat&quot;,
 &quot;full_name&quot;: &quot;codecombat/codecombat&quot;
 }
 }
 }
]
</code></pre>
Each object in the array is a pull request (PR), filtered by the <code>base=target</code> branch, which we specified to be <code>master</code> in our <code>curl</code> command above.
The JSON actually contains much more information than this; I've just removed most of it to show the relevant parts for this question.
<h3>Parsing the cURL Response</h3>
You could probably write a Python/Ruby/PHP/Whatever script to then parse out the <code>html_url</code> property of each pull-request and list it on the command line. For example, here's a simple Ruby script that will parse the output of a JSON response saved from the <code>curl</code> output:
<pre class="lang-ruby prettyprint-override"><code>require 'json'

json = JSON.parse(File.read('./pulls.json'))
pulls = json.map { |pull| { title: pull['title'], url: pull['html_url'] } }

pulls.each do |pull|
 puts pull.values
 puts
end
</code></pre>
Which outputs the following:
<pre class="lang-none prettyprint-override"><code>$ ruby parser.rb
Update es-ES.coffee
https://github.com/codecombat/codecombat/pull/879

Fix deltas referring to last system saved
https://github.com/codecombat/codecombat/pull/874

Refactor getNameById and add naming to systems in deltas
https://github.com/codecombat/codecombat/pull/866

Traducido varios textos del fichero es-ES.coffe al espa├▒ol de Espa├▒a
https://github.com/codecombat/codecombat/pull/865

Anon name collide
https://github.com/codecombat/codecombat/pull/834
</code></pre>

blocks|key|2765824|text|是的，你能做到。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2765825|在Github的术语中，"to+branch“是"base”，所以搜索短语是：is:open+is:pr+base:X|offset|length|style|CODE|2765826|官方描述：Search+based+on+branch+names|2765827|您也可以选择添加is:merged或is:unmerged过滤器。|2765828|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.github.com/en/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-by-branch-name^0|0|13|K|0|5|S|0|0|8|9|I|B|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|K|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Yes, you can do it.
In Github's terminology the &quot;to branch&quot; is &quot;base&quot;
So the search phrase is: <code>is:open is:pr base:X</code>
Official description: <a href="https://docs.github.com/en/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-by-branch-name" rel="noreferrer">Search based on branch names</a>
Optionally you can add <code>is:merged</code> or <code>is:unmerged</code> filters as well.

blocks|key|170018|text|现在GitHub+CLI已经可用，下面介绍如何为给定的存储库执行此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|170019|您可以按照适用于您的操作系统和首选软件包管理器的appropriate+instructions安装gh命令行界面。|style|CODE|170020|我使用cli/cli存储库来演示：|170021|gh+pr+list+--base+trunk+-R+cli/cli|170022|输出：|170023|#3045++[hackday]+mergeconflict++++++++++++++++++++++++++++++++++++++++++++++++++hackday2102
#3044++Isolate+test+suite+from+environment+variables++++++++++++++++++++++++++++env-tests
#3042++Remove+functionality+to+add,+view+and+edit+binary+files+in+gists+++++++++g14a:bug/gist-binary-files
#3023++Issue/pr+create:+exit+with+nonzero+status+code+when+"Cancel"+was+chosen++cancel-error-status
#3018++Add+`pr+create+--body-file`+flag+++++++++++++++++++++++++++++++++++++++++castaneai:pr-create-body-file
#3010++Add+`api+--cache`+flag+++++++++++++++++++++++++++++++++++++++++++++++++++api-cache
#3008++Add+interactive+select+in+gist+view++++++++++++++++++++++++++++++++++++++ganboonhong:interactive-gist-view
#2997++Feature/add+files+to+gist++++++++++++++++++++++++++++++++++++++++++++++++g14a:feature/add-files-to-gist
#2991++Repo+create+tweaks+++++++++++++++++++++++++++++++++++++++++++++++++++++++repo-create-prompt-change
#2953++Add+`repo+list`+command++++++++++++++++++++++++++++++++++++++++++++++++++cristiand391:add-repo-list
#2923++[WIP]+first+round+of+actions+support+++++++++++++++++++++++++++++++++++++actions
#2728++Better+completions+++++++++++++++++++++++++++++++++++++++++++++++++++++++rsteube:better-completions
#2261++pr+status:+show+number+of+approvals++++++++++++++++++++++++++++++++++++++despreston:des/approval-count
#2160++Sign+Windows+.exes+in+a+post-build+hook++++++++++++++++++++++++++++++++++mbpreble:sign-windows-executables
#2080++store+gh+config+in+%25APPDATA%25+on+windows+os+++++++++++++++++++++++++++++++RozzaysRed:appdata_configPath|code-block|syntax|javascript|170024|entityMap|0|LINK|mutability|MUTABLE|url|https://cli.github.com/|1|https://github.com/cli/cli#installation^0|2|A|0|0|1E|2|O|O|1|0|3|7|0|0|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@$A|17|B|18|F|G]]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|H|3|I|5|6|7|1C|8|@$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1F|8|@$A|1G|B|1H|F|G]]|9|@]|C|$]]|$1|L|3|M|5|6|7|1I|8|@]|9|@]|C|$]]|$1|N|3|O|5|P|7|1J|8|@]|9|@]|C|$Q|R]]|$1|S|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

Now that the <a href="https://cli.github.com/" rel="nofollow noreferrer">GitHub CLI</a> is available, here's how you would do it for a given repository.
You can install the <code>gh</code> CLI following the <a href="https://github.com/cli/cli#installation" rel="nofollow noreferrer">appropriate instructions</a> for your OS and preferred package manager.
I use the <code>cli/cli</code> repo to demonstrate:
<code>gh pr list --base trunk -R cli/cli</code>
Output:
<pre><code>#3045 [hackday] mergeconflict hackday2102
#3044 Isolate test suite from environment variables env-tests
#3042 Remove functionality to add, view and edit binary files in gists g14a:bug/gist-binary-files
#3023 Issue/pr create: exit with nonzero status code when &quot;Cancel&quot; was chosen cancel-error-status
#3018 Add `pr create --body-file` flag castaneai:pr-create-body-file
#3010 Add `api --cache` flag api-cache
#3008 Add interactive select in gist view ganboonhong:interactive-gist-view
#2997 Feature/add files to gist g14a:feature/add-files-to-gist
#2991 Repo create tweaks repo-create-prompt-change
#2953 Add `repo list` command cristiand391:add-repo-list
#2923 [WIP] first round of actions support actions
#2728 Better completions rsteube:better-completions
#2261 pr status: show number of approvals despreston:des/approval-count
#2160 Sign Windows .exes in a post-build hook mbpreble:sign-windows-executables
#2080 store gh config in %APPDATA% on windows os RozzaysRed:appdata_configPath
</code></pre>

I'm working on a GitHub repo with lots of branches and pull requests.

Let's say, for example, that I have the following pull requests:

<ul>
<li><code>a</code> to branch <code>X</code></li>
<li><code>b</code> to branch <code>X</code></li>
<li><code>c</code> to branch <code>Y</code></li>
<li><code>d</code> to branch <code>X</code></li>
<li><code>e</code> to branch <code>Y</code>.</li>
</ul>

Is there a way to find all the pull requests that are targeted for branch <code>X</code> (i.e. <code>a -&gt; X</code>, <code>b -&gt; X</code>, <code>d -&gt; X</code>)?

How can I filter all GitHub pull requests for a specific target branch

包管理器

Windows

Python

GitHub

JSON

我正在开发一个包含大量分支和拉取请求的GitHub存储库。例如，假设我有以下拉取请求：a到分支Xb到分支Xc到分支Yd到分支Xe到分支Y.有没有办法找到所有针对分支X (即a -> X、b -> X、d -> X)的拉取请求？

问如何过滤特定目标分支的所有GitHub拉取请求
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何过滤特定目标分支的所有GitHub拉取请求EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何过滤特定目标分支的所有GitHub拉取请求
EN