合并到GitHub pull请求中,可能首先对它们进行更改 [英] Merge in GitHub pull requests, possibly making changes to them first
问题描述
我最近开始在GitHub上管理一个项目,人们一直在提交pull请求。我希望能够:
-
首先审查它们以确保它们实际工作
可能在合并到主人面前进行一些文体修改 我怎样才能做到这一点? First vet them to make sure they actually work
Possibly making some stylistic changes before merging to master
$ b
$ b $您需要创建一个单独的分支,比如dev,并且指示人们在合并到master之前对其进行编码? b
github帮助页面,其中详细说明了如何通过在本地签出拉取请求来更改拉取请求。
我可能会尝试的是创建拉请求提交程序的远程(我使用上面的例子):
git remote add kneath git ://github.com/kneath/jobs.git
获取更改:
git fetch kneath
检出有问题的分支(例如master):
pre $ g $ git checkout kneath / master
不管你喜欢什么,都可以使用它们,因为在那里的代码会有拉取请求代码。运行测试等。
如果您愿意,可以将它们合并:
git checkout master
git merge kneath / master
另外,这里是git 项目管理工作流程上的一个非常好的页面,详细介绍了可用于协作的各种工作流程整合。
I recently started managing a project on GitHub where people have been submitting pull requests. Rather than merge them to master, I would like the ability to:
How can I do this?
Do you have to make a separate branch, such as "dev", and instruct people to code against that before you merge to master?
There is a github help page on this which details how to make changes to a pull request by checking out pull requests locally.
What I might try is first creating a remote for the pull request submitter (I'm using the examples from the above page):
git remote add kneath git://github.com/kneath/jobs.git
Fetch the changes:
git fetch kneath
Check out the branch in question (ex. master):
git checkout kneath/master
Vet them however you like, since the code that will be there will be the pull request code. Run tests, etc.
Merge them in if you're good to go:
git checkout master
git merge kneath/master
Further, here is a very good page on git project management workflows which details the various workflows one can take on collaboration integration.
这篇关于合并到GitHub pull请求中,可能首先对它们进行更改的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!