Save the patch somewhere. If you’re using linux you can use curl: curl -L https://github.com/JustinTulloss/zeromq.node/pull/47.patch > /tmp/47.patch To apply the patch use git apply. You can see if the patch will apply cleanly with the check option. Change to your git directory and run: git apply –check /tmp/47.patch If it looks like you want to … Read more
You can just use the git flow feature publish <name>this will publish your feature branch to your origin (like Bitbucket). Then you can create the pull request there and merge it into develop. After that is done, you need to manually delete the local feature branch. The only command you can not use is git … Read more
You can use git request-pull to achieve the same kind of workflow (which is improved with Git1.7.9+). See the article “using signed tag in pull-requests” A typical distributed workflow using Git is for a contributor to fork a project, build on it, publish the result to her public repository, and ask the “upstream” person (often … Read more
2 years and a half years later, (February 2019), do check if the new button “Re-request review” would help. As illustrated on twitter, if your PR was already reviewed, but now it’s time for round 2: With fresh eyes and fresh code, re-request a review 🔃 Note/caveat: (from “Requesting a pull request review“) Pull request … Read more
I assume your origin is your own fork of some project that you want to do a pull request too? Since you will be changing history (by resetting the head) you will need to push with –force flag. Locate the hash of your last good commit using git log. Now run git reset SHA This … Read more
Prefixing any search qualifier with a – excludes all results that are matched by that qualifier. For example, you might be interested in finding all “cats” repositories with more than 10 stars that are not written in JavaScript: cats stars:>10 -language:javascript You might also want to find all issues mentioning @defunkt that are not in … Read more
You can’t ignore some files from a pull request selectively. Two workarounds for this can be – First – Create a new branch from ‘release’ Replace the non-required files from ‘master’ Create pull request from this new branch Second – Create a new branch from ‘master’ Put changes of required files from ‘release’ Create pull … Read more
So, you can’t customize the conditions of the trigger, but as LeGec mentions you can customize your code to only trigger when the Pull Request is merged. To do that, make sure your script responds to the PullRequestEvent. The conditions to test are: “action” is “closed“ “merged” (inside of “pull_request”) is true This way your … Read more
You don’t actually have a pull request; GitHub just sees that you’ve pushed a branch, and is offering to create a pull request for it if you want. If you don’t care about that, just ignore it. It’s completely harmless and will go away as soon as GitHub doesn’t think the branch is “recent”.
As you mention in the comments, the merge from the pull request will result in a commit. It is on that commit message you can add a “close #xx” in order to trigger the closing of an issue. However, as mentioned in “Closing multiple issues in Github with a commit message”, in GitHub blog post … Read more