pull-request

问题 Excuse me but this may be a noob question but it jsut crossed my thoughts and I think it is worth to fix my ideas and get a relevant explanation from some experts. I remember (I may be wrong) that when I submitted some pull requests to some repository, when the PR is merged to the master (or other branch), I'm notified about that action and when accessing the PR url I can see a sort of This PR has been merged into... message. Just browsing an old issue, I can no more see that kinf of message

问题 A bunch of questions ask how to rewrite ( rebase ) some commits so that they appear on a branch, but these all seem to assume that rebase is actually necessary, i.e. that the commits wanted for the branch are interspersed with commits wanted on master (whether made by “you” or others). This question is simpler: I have a clone of a repository on the master branch, and I made a bunch of commits intending to create a GitHub pull request. Normally I would have run git checkout -b new-feature

问题 We use TFS 2017 (15.117.26714.0) with git. When we try to make a pull request, TFS says "Pull request cannot be automatically merged.". I'm just trying to figure out what's happening but I didn't find any message on why the pull request cannot be automatically merged. Do you know how to debug "Pull request cannot be automatically merged."? Is there a hidden option or a link to a log that can help me? Update You can find a little report about the job that is supposed to execute the merge

问题 I'm not getting anywhere with this... trying to make 2 separate pull requests. Maybe someone can point me to what is wrong. Here is what I'm doing: Fork repo FOO and clone to my machine git clone https://github.com/myself/FOO.git Set upstream to track FOO git remote add upstream https://github.com/maker_of_FOO/FOO.git Create new branch and checkout git branch FOO_fix_1 git checkout FOO_Fix_1 Edit files and commit and push git commit git push Push new branch to my fork of FOO git push -u

问题 I use GitHub client for Bitbucket repository. All work & sync correctly, but Pull Request button not showing. In GitHub repo all works. I found simular issue - Github for Mac: Pull Request Button is missing, but I use Bitbucket and can't change repo marker from "other". Any proposal? GitHub: Other repo: 回答1: Answer from official github support ( support@github.com ): In order to create a pull request the repository must exist on GitHub.com. and There is a button called 'View Branch' beside

问题 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

问题 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? 回答1: 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

问题 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. 回答1: The

问题 Is there a way to find out the acceptance rate of one's GitHub PR's, probably using the API? While at that, it would be interesting to find out how many of the issues I reported have been closed vs. are still open, across all repos. 回答1: I don't see a way to get that information directly. That leaves you with the GitHub Issues Events API. With that, you can list all the events of a repo: GET /repos/:owner/:repo/issues/events https://api.github.com/repos/user/reponame/issues/events And filter

问题 When I create pull request, I can see two options as Reviewers and Assignees . What is difference between those? I think this is from any of last version of github. 回答1: Reviewers and assignees are a tool for organizing who is working on what pull request and issue. They don't confer any extra permissions. Reviewers are people you are specifically requesting to review your pull request. From the docs... Pull request authors and repository owners and collaborators can request a pull request