pull-request

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? Pull requests are based on a branch. The only way to open up a pull request for multiple commits is to isolate them into their own branch, and open the pull requests from there. The easiest way I've

Pull Requests are great for understanding the larger thinking around a change or set of changes made to a repo. Reading pull requests are a great way to quickly "grok" a project as, instead of small atomic changes to the source, you get larger groupings of logical changes. Analogous to organizing the lines in your code into related "stanzas" to make it easier to read. I find myself looking at a file or a commit, and I wonder if there is a way to backtrack the commit to the Pull Request that originally created it. That Pull Request would have been merged eventually, but not necessary with a

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? 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 present there ( git pull from the other repo). A "pull request" is you requesting the target repository to

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. 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 https://github.com and https://api.github.com . diffie-hellman-group1-sha1: This applies to all SSH

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 GitHub API Plugin 1.44 I spent a long time on this. The above comment "if I leave this field blank"

My team is experimenting with using GitHub pull requests for code reviews. My only question is what do you do with the branch after you're done? I would think you'd want to delete the branch, but since GitHub hides branches that have been merged into your current branch, it seemed like maybe I should keep it. Just curious on what your thoughts on best practices for this are. Bill Door The rule of thumb that we use (which is here some where on Stack Overflow) is "branches are for work, tags are for history". Whenever a branch is merged (most likely into master) we tag the merge point using the

I've opened a pull request to a project. The maintainer has decided to accept it, but told me to modify some contents. How can I do it? Whether I should keep the commit hash unchanged, how can I do it? just push more commits on to the branch the request is for. The pull request will pick this up then Example: If you want to have b merged into master You push c1,c2,c3 to b then you make a new request for b it gets reviewed and you need more commits You push c11,c21,c31 to b The pull request now shows all 6 six commits I just had one commit in a pull request, and I used git commit --amend to

I'm not sure, but I have a vague memory of creating a github pull request with "Issue 4" or something in the title, and it automatically attached itself to Issue 4 in the project that I was submitting it to. I tried it again recently and it didn't work -- it just created a brand new issue instead. I don't see any options like "Attach to issue" on the new pull request page, nor "Open a new pull request for this issue" on the issue page. Is there any way to do this, to help project owners keep their Issues page clean and avoid duplication? Edit : To clarify, I know that creating a pull request