过滤Github上的问题,将通过拉取请求来关闭? [英] Filter issues on Github that will be closed by a pull request?

查看:108
本文介绍了过滤Github上的问题,将通过拉取请求来关闭?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个存在几个公开问题的存储库。在一个提交中,你可以引用一个问题将被关闭,这些都在GitHub中注明,当一个请求完成时它们将被关闭。



一旦这些被检入,我希望能够忽略它们,同时寻找新的bug来解决。



澄清,有四种类型的问题我在看: / b>


  1. 已关闭的问题(易于识别)



  2. 打开的问题将在未来的某个时间点通过拉取请求被关闭。 >已打开的问题,但没有将要关闭的拉取请求

有没有办法过滤掉Github上的问题,这些问题将被未来的pull请求(即类型3和4)关闭? 解决方案

否,你现在不能在Github上做这件事。


I have a repository with a few open issues. In a commit you can reference an issue will be closed, and these are noted in GitHub that they will be closed when a pull request is complete.

Once these are checked in, I'd like to be able to ignore them while looking for new bugs to address.

For clarification, there are four types of issues I'm looking at:

  1. Issues which are closed (these are easy to identify)
  2. Issues which are open (still easy to identify)
  3. Issues which are open but will be closed at some point in the future by a pull request.
  4. Issues which are open but have no pull request that will close then.

Is there a way to filter out issues on Github that will be closed by a future pull request (i.e those of type 3 and 4)?

解决方案

No, you cannot do this presently on Github.

这篇关于过滤Github上的问题,将通过拉取请求来关闭?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆