pull-request

问题 I have a repo iontech/Anagen forked from agiliq/Anagen I made a few commits to my fork and added a tag. Then I opened a Pull Request. This Pull Request includes only my commits. How do I include the tag I've created into the Pull Request? 回答1: How do I include the tag I've created into the Pull Request? You can't. A pull request does not include tags. A pull request is only a pointer to a thread of commits (a branch) in your repository that you're proposing another repository to merge. If you

问题 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: First vet them to make sure they actually work Possibly making some stylistic changes before merging to master 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? 回答1: There is a github help page on this which details how to make changes to a pull

问题 My project on GitHub has received a pull request. The pull request only partly fixes the issue that it's addressing. I've pulled in the changes to a local branch and added some commits of my own. I'd now like to push those commits back to my remote repo and have them show up on the pull request, but without merging them into the target branch. I'd like to keep the pull request open for further review and discussion, and potentially further commits. Is there a way I can add commits to the pull

问题 I'm trying to review a pull request on GitHub to a branch that isn't master. The target branch was behind master and the pull request showed commits from master, so I merged master and pushed it to GitHub, but the commits and diff for them still appear in the pull request after refreshing. I've doubled checked that the branch on GitHub has the commits from master. Why are they still appearing in the pull request? I've also checked out the pull request locally and it only shows the un-merged

问题 I've cloned a repo (made sure to mark the original repo as upstream ) and went the gitflow way: create a develop branch from which all new features are created and commited back to. Every push to Master from develop is by definition a release, meaning master is always deployable. I like this setup a lot. Now sometimes aside from this flow I may want to contribute back to upstream some feature that I keep in separate feature-branches. However since a feature-branch is created from develop HEAD

问题 I am looking for some command which tells me number of files committed in a single pull request. I would like to know count of files in a single pull request individual from beginning. Question explained in real life scenario: Let's say for some myProject someone raised a pull request number 100 which has changes in 15 files. I am looking for a command which list all pull request from 1 to 100 with count of changed files. Please answer wrto Windows 7. i.e. PR Number 100 has changes in 10

问题 I have a set of documentation for my company's API, based on the excellent Slate framework from TripIt. Per instructions, I forked their repo and proceeded to customize it. That fork lives here. The obnoxious thing is that when contributors in my organization do a new pull request, the "base fork" on the Github "Comparing Changes" screen defaults to TripIt's repository, not my fork. They've more than once sent pull requests to the wrong place. Telling people "don't do that" isn't a

问题 Here's the scenario: I have a public repo A . Bob forks A , adds a few commits to Bob/master and submits a pull request to merge those changes in A/master . I'd like to make a few changes to the proposed pull request before merging it back to A/master . How can I do that if I can't push to Bob/master ? 回答1: There are a number of workflows you can use here. Some examples are: Comment on the pull request, and have Bob make some changes. See Pull Request Discussion for more info. Merge the pull

问题 I made some changes I submitted a pull request The pull request was accepted and merged. We found a bug The changes were removed again whilst I fixed the bug. I've now fixed the bug and want to resubmit the pull request with 1 extra commit. Is there any way to reopen the pull request or update it, or do I have to create a new pull request, type out the description etc again? Gitorious has this feature and we've recently moved to GitHub. 回答1: The answer seems to be: You can't. Once a pull

问题 On Github, you can make pull requests to add functionality to a project. One's contributions have to be on a branch that, if the request is accepted, will be merged into the master branch (or an analogous one) of the project. Now, I submitted a pull request on Github and my contributions are on a branch called patch-1 . I can modify the name of the branch locally by git branch -m patch-1 newname and in principle I can also rename it on my forked repo on Github by following the instruction