pull-request

问题 In one commit, I have changed several files in several folders, say, folderA , folderB , and folderC . In folderA the changes are just adding comments and some code for printing intermediate results, which serve my own understanding. folderB , folderC are newly created, in there I have written some code for the project, now I want to only send a pull request for folderB and folderC , how would you do that? Either working from the github webpage or the command line will be helpful. 回答1: You

问题 How can I get the Pull Request Id via a Build Id? Is there any existing Rest API to support this? 回答1: You can get the build details with Builds - Get Rest API (you just need the Build Id): GET https://dev.azure.com/{organization}/{project}/_apis/build/builds/{buildId}?api-version=5.0 In the JSON response, you got also the Pull Request Id: "parameters":"{ \"system.pullRequest.pullRequestId\":\"1\",\"system.pullRequest.sourceBranch\":\"refs/heads/build\",\"system.pullRequest.targetBranch\":\

问题 I've been trying to get the build on PR working for some time now following the usual guides. However i ran into some issues. Here is what i added to the previously existing configuration @ Jenkins project: Source Code Management: Multiple SCMs - Repository URL: ssh://git@git.company.pt/projectCode/RepName.git - Credentials with ssh key working - Batches to build: */${sourceBranch} - Repository browser: auto - Additional Behaviours: none Build triggers: - Poll SCM And the the previous working

问题 So my question was kind of addressed by this post, but I'm still a little confused. Basically, I'm checking out a repo on GitHub, and I see that there are currently 34 open and 173 closed pull requests. My current understanding is this: If somebody makes a stupid pull request, the maintainers will close it If somebody makes a legit pull request, the maintainers may merge it, at which point the request is closed If a request is open (legit or not) then that means the maintainers just haven't

问题 A follow-up question to my answer about editing GitHub pull-requests asked whether editing the patch file directly before applying it would result in taking credit for the original author's work. Since it wasn't really part of the original question, I'm asking it here as a new question. 回答1: TL;DR Git will attribute authorship to the creator of the patch and not the current committer. However, you can override this behavior, How Git Handles Patches in Mailbox Files The git am command

问题 While making pull request in github and reviewing changes we got Diff Truncated error as shown below Can anyone help to fix this issue 回答1: It is possible the pull request triggers one of the limits mentioned by GitHub support. Brian Levin @github: We have some limits on diffs that we show in the browser in order to keep the pull request and compare pages working. Currently, we cut them off at: 300 files, a total diff of 1MB, and an individual diff of 100KB. If your diffs exceed the limits

问题 In short; we want to use a build definition to both generate artifacts for Release Management and checking Pull Requests, but not allow the latter to trigger a new release. We have CI build definition on our Git Repo feeding artifacts into a Release Management Pipeline. Like many teams we also have Pull Requests set up to protect our git master. We'd like to reuse our CI build to validate Pull Requests before they are merged in but doing so automatically triggers our release pipeline

问题 What are the relations between git pull-request and git pull and git push ? Suppose I and other peers share a remote repository. Each of us has an individual local repository. When I finish working on a feature in my local repository, I would like to share my work with my peers. Shall I use git pull-request to ask my peers to git pull from my local repository to their individual repositories? Shall I run git pull-request with the shared remote repository as its URL argument? If yes, does the

问题 In our business we have the following setup (hugely simplified version), pretty standard: A master branch, which updates the live environment through a hook. A test branch, used for QA, UA, which updates a test environment in the same way. The repo is hosted on GitHub. The workflow is usually as follows: Pull from master Create a branch e.g. Ticket1 to work on the particular ticket Do the work, test locally Commit and push branch Ticket1 Merge Ticket1 into test through a pull request in

问题 The only workaround we found for validating pull requests in visual studio online currently is to create a visual studio build definition that triggers our jenkins job, and create a branch policy on that build definition. But Visual Studio online is able to trigger the jenkins job directly when a git pull request is created / updated. Is it possible to create a branch policy on the outcome of that jenkins job? The TFS plugin already provides status feedback for the "normal push" build status.