pull-request

How do I find out who closed a pull request using the Github API? e.g. this pull request was opened by myakura, closed by markdotto. But https://api.github.com/repos/twitter/bootstrap/pulls/4461 doesn't show any reference to markdotto. 来源： https://stackoverflow.com/questions/12033171/github-api-find-out-who-closed-a-pull-request

Someone has submitted a pull request to my GitHub project from a fork. Rather than merging directly into master, I would prefer to merge the changes into a feature branch so that I can make some minor edits before merging the final product into master. If at all possible, I'd like GitHub to indicate to the submitter that the request was accepted (I want to encourage and recognize contributions!). Is this possible? How do I go about it? It would be nice if you could change the merge target of a pull request. It would also be nice if you could collaborate on a pull request before accepting it to

I have multiple accounts in git I committed code three weeks back with this account. I'll unable to pull my code . I was getting The requested URL returned error: 403 I'll try Pushing to Git returning Error Code 403 fatal: HTTP request failed but I couldn't solved my error git -c diff.mnemonicprefix=false -c core.quotepath=false fetch origin remote: Forbidden fatal: unable to access 'https://chantidurgam@bitbucket.org/chantidurgam/patanjali.git/': The requested URL returned error: 403 Completed with errors, see above. Kunal I had the same issue when using the git cli and sourcetree - and doing

We use Git hosted in Azure DevOps for all of our source code. So far we have used Git Hooks to ensure that team members follow a branch naming convention {branchtype}/{username}/{friendlyname}/{workitemtype}{workitemid} . Examples: dev/dparkar/addauth/ta123456 hf/jsmith/memoryleak/bu11111 The branch naming convention allow us to clearly understand whether it's a regular development branch or a hotfix branch and which work item it is associated with, among other things. To setup Git Hooks locally, team members were required to run a script locally before starting to contribute. This was fine as

I used git flow feature finish to finish a feature branch. I use the AVH fork of git-flow, which deletes the remote feature branch - but the Bitbucket pull request is still open. How should I close the Bitbucket pull request? And what is a correct way to accept a PR in future while following the git flow workflow? While the AVH version of git-flow deletes the remote feature branch when you do git flow feature finish , strangely, it doesn't push anything. It leaves you on the master branch, so once you've done git push or git push origin master:master , the BitBucket pull request will

This is the workflow we currently follow: Finish a feature and merge it into develop branch Create a release branch from develop Run build scripts on release branch Create a pull request to merge the release branch into master Accept the release branch pull request and merge The master branch can then deploy to live server by running deploy command This all works great, except in my Git repo my branches are out of sync master is now behind develop because it doesn't have the merge commits that happened from the pull request merging the release branch into develop . But master is also ahead of

My current workflow requires a version Bump on every PR, so I would like to take advantage of that and automatically create a tag on GitHub on every PR merge, so it appears in the "release" section. I've seen that I can write a post-merge hook. My doubt is if that hook runs locally in my machine, remotely on GitHub, or both (given that I merge the PR on GitHub, and not locally. What's the case? I can write a post-merge hook. My doubt is if that hook runs locally in my machine, remotely on GitHub, or both It will certainly not run on GitHub (that wouldn't be safe for GitHub to run any user

I've got a repo on Bitbucket that only I have write access to. Someone forked that repo, made changes and issued a pull request to my repo from the fork. How can I get that pull request as a git patch to apply temporarily to my repo for testing purposes? The forked repo is private so I can't pull it down, and I wouldn't want to do that anyway. On GitHub you can simply go to a pull request and add a .patch to the end of the url to download the patch. This doesn't work with Bitbucket. Lythom The Pull Request Patch is available through bitbucket API (despite there is no button to download it