pull-request

问题 I downloaded a trunk version of a codebase from git, and there are build errors. Aparently a patch is now available, and I received an email : see https://github.com/JustinTulloss/zeromq.node/pull/47 for patch I am new to git so I'm not quite sure what to do with this 'patch' especially, since the page looks more like a discussion thread. Does anyone know how I can obtain/apply this patch to my locally cloned git repository? 回答1: Save the patch somewhere. If you're using linux you can use

问题 I have forked project at github. I make one commit and pull request it. This commit was approved. Then i make second commit and pull request it too. But in pull request there were 2 commits: my second commit and old commit which was approved. How can i sync my repository and main repository? 回答1: Merge back from the upstream repository, or create the new pull request on a new branch. Or rebase on top of upstream: git remote add upstream (url-for-upstream-repository) git fetch upstream git

问题 The terminology used to merge a branch with an official repository is a 'pull request'. This is confusing, as it appears that I am requesting to push my changes to the official repository. Why is it called a pull request and not a push request? 回答1: If you have a code change in your repository, and want to move it to a target repository, then: "Push" is you forcing the changes being present in the target repository ( git push ). "Pull" is the target repository grabbing your changes to be

问题 I am getting error at the time of - git pull , Error is “ Fatal: unable to access 'https://github.com/repository.git/': error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number?” . Please suggest solution. 回答1: The Op mentions my problem is fixed. Internet speed was very slow so issue occurs. But do also consider that GitHub disabled just yesterday (Feb. 22 2018) deprecated algorithms: TLSv1/TLSv1.1: This applies to all HTTPS connections, including web, API, and git connections to

问题 Yesterday my pullrequest jobs failed with the following output: 11:07:41 > git rev-parse origin/${sha1}^{commit} 11:07:41 > git rev-parse ${sha1}^{commit} 11:07:41 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. I have made an investigation and saw that in property ${sha1} there was nothing. When i paste an absolute path to pull request builder like pr/341/merge instead of ${sha1} the build works. What it can be? Git Client Plugin 1.9.0

问题 When I open a pull request on GitHub. All commits since my last request and all new ones are automatically added to this request . I can't seem to control which commits are added and which are not. When I try to open another pull request, I get an "Oops! There's already a pull request" error. Is there any easy way to open multiple pull requests without having to mess around with the command line? 回答1: Pull requests are based on a branch. The only way to open up a pull request for multiple

问题 This question already has answers here : Squash my last X commits together using Git (32 answers) Closed 2 years ago . I made a pull request on GitHub. Now the owner of the repository is saying to squash all the commits into one. When I type git rebase -i Notepad opens with the following content: noop # Rebase 0b13622..0b13622 onto 0b13622 # # Commands: # p, pick = use commit # r, reword = use commit, but edit the commit message # e, edit = use commit, but stop for amending # s, squash = use

问题 It seems like you have to interact with github.com to initiate a pull request. Is this so? 回答1: UPDATE : The hub command is now an official github project and also supports creating pull requests ORIGINAL : Seems like a particularly useful thing to add to the hub command: http://github.com/defunkt/hub or the github gem: http://github.com/defunkt/github-gem I suggest filing an issue with those projects asking for it. The github guys are pretty responsive. 回答2: Git now ships with a subcommand

问题 Let's say that GitHub repo B sends a pull request to GitHub repo A , and suppose that the pull won't go through without resolving some conflicts and merging. Therefore, in order to accept the changes proposed by B , the owner of A makes the pull request from an offline repo, performs the merge, and pushes the merge to A . Now A is at least one commit ahead of B . How does B now update itself to be in sync with A ? Can this be done entirely from within the GitHub web interface? (I imagine that

问题 I need to merge my own pull request feature branch onto my local repo's master branch. However, if the upstream maintainer merges my pull request, I'll have to pull in another merge commit. Git doesn't realize that I already merged the same branch before, so instead I have 2 merge commits for the same branch. How do you guys sync your local and upstream repositories without duplicate merge commits? 回答1: If I understand you correctly, your status is more or less this: (Black = upstream, blue =