问题描述
我特别感兴趣的是拉请求，编辑问题和绑定提交，以及我通常必须使用的其他事情 for。不过，我已经开始使用magit，真的喜欢键盘和一般的界面---我也想留在这个部分的emacs，而不是需要保持额外的shell打开拉请求，问题等。
I'm specifically interested in pull requests, editing issues and tying them to commits, and other things I generally have to use hub on the command line for. However, I've started using magit and really like the keybindings and general interface---I'd like to stay in emacs for this part, too, rather than needing to keep an extra shell open for pull requests, issues, etc.
可以添加最多github功能的软件包，我可以找到的是：
The packages that might add the most github functionality to magit that I could find are:
- Magithub
- magit-gh-pulls
- gh.el
任何可能参与这些项目的人都可以推荐他们如何比较和最好的将拉动请求集成到Magit环境中？
Can anyone, possibly involved with these projects, recommend how they'd compare and what might be best for integrating pull requests into a magit environment?
推荐答案
最终我将在Magit中实现这样的事情（我是维护者），但是我首先要得到一个释放。
Eventually I will implement such things in Magit (I am the maintainer), but I first have to get a release out.
不幸的是，目前还没有第三方扩展这可以填补这个角色。现在已经破坏了 magithub 。 magit-gh-pulls （由Yann，我的前任Magit维护者）也没有与Magit的变化保持同步。我试图在一段时间之前解决它，但是当它变得清楚的时候放弃，这样做会导致完全重写。 gh.el 也由Yann编写，由 magit-gh-pulls 使用。过去我已经做出了贡献，但最终停止使用它，因为（a）它使用 url.el ，结果是非常不可靠的（b）它是复杂的。
Unfortunately there currently also isn't a third-party extensions that could fill this role. magithub has been broken for a long time now. magit-gh-pulls (by Yann, my predecessor as Magit maintainer) also wasn't kept in sync with the changes in Magit. I tried to fix it up some time ago, but gave up when it became clear that doing so would result in a complete rewrite . gh.el is also written by Yann and is used by magit-gh-pulls. I have contributed to it in the past but eventually stopped using it because (a) it uses url.el and that turned out to be very unreliable (b) it's over complex.
所以恐怕目前还没有一个你想做的包。如果你想自己写，我建议你使用 request.el ，然后只实现你实际需要的Github api的那些部分，以免过度工程。
So I am afraid there currently isn't a package that does what you want. If you want to write it yourself, I recommend you use request.el and then only implement those parts of the Github api that you actually need, to avoid over-engineering it.
编辑：截至2015年10月 magit-gh-pulls 是，但不再是正式的扩展名。就我个人而言，我不会使用它，因为我认为它应该或多或少。我目前以库。即使我维护这个图书馆，我也不认为这是官方的扩展 - 它是按原样提供的。这个功能非常基本，你给它一个问题号码，它为你创建一个分支，就是这样。
As of October 2015 magit-gh-pulls is maintained again, but no longer an official extension. Personally I don't use it, as I think it should either to more or less. I currently use "less" in the form of magit-branch-pull-request from the magit-rockstar library. Even though I maintain that library, I do not consider it an official extension - it's provided as-is. That function is very basic, you give it an issue number and it creates a branch for you, that's it.
在2016年9月编辑：我已经写了和作为替代 gh.el 。它们主要是为了我自己的个人使用，并且提供 ，基本上它们给你的功能，如 ghub-get（resource&可选参数数据noerror），那么你必须看看各自的api文档，找出什么资源， params 和 data 你必须使用。此外，错误处理不是很好，目前使用 url.el 。我打算最终通过使用 libcurl 在发布具有ffi支持的Emacs之后的时间内完善。
Edit in September 2016: I have written ghub.el and glab.el as replacements for gh.el. They are mostly intended for my own personal use and provide very little, basically they give you functions such as ghub-get (resource &optional params data noerror), you then have to look at the respective api documentation to figure out what resource, params, and data you have to use. Also the error handling isn't great and this currently uses url.el. I intend to improve both eventually by using libcurl some time after an Emacs with ffi support has been released.
这篇关于大多数开发的magit / github扩展为emacs的拉请求的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！