pull-request

I have a comprehensive step by step description on how I do this and I wanted to share it here so developers can benefit from it (I'll answer my own question). Since changes contributed to open source projects will have to be peer reviewed it's common to see a workflow which relies on git pull requests. Pull requests are not allowed from directly cloned repos (you need your own fork). So these are the steps I follow to maintain a healthy fork and contribute to an open source periodically: Note: Steps 1, 2 and 3 are only done once on a single development machine to set everything up: 1) Make

I cloned this repo on my computer: https://github.com/derobins/wmd.git There are several bugs with it though, and it looks like another user has fixed them and issued "Pull requests" (I assume these are requests for their changes to be committed?) Is it possible to merge those changes into my local version? EDIT: just to be clear, this is not my repository. I am using the WMD editor from derobins, but it has several bugs which those pull requests purport to fix. I have cloned the repo on Ubuntu (not in github) and was hoping to merge those changes in if possible. Mark Longair (GitHub has very

How does one set up a code review using Gitlab? I see it listed as a feature on the Gitlab website, but I can't seem to find instructions on how to set one up (For that matter, any link to a Gitlab user manual would be most appreciated). Some of my searching has indicated that 'Merge Requests' are the way to go... but I'm finding them limiting. An issued merge request shows all of the commits between one branch and the other. I seem to only be able to view diffs generated for each individual commit. For example, let's say I have a file I want to review. It is a new file but I've submitted

To put it in "BDD" terms: Background: Given I'm contributing to a GH repo When I create a pull request Then Travis should build the latest commit When I push to an existing pull request Then Travis should build the latest commit When I merge a pull request to master Then Travis should build master I was confused by Travis-CI's "build pushes" and "build PRs" settings, as: Enabling both causes each Pull Request to be build twice by Travis once for the commit on that branch and once again for the merge commit of that branch into its destination Enabling just "build PRs" causes PRs to be built,

In this project I'm working on, I'm supposed to commit my progress to a repo using pull requests, and every commit has to be in a different branch. The problem is that the last 3 commits were pushed in a single pull requests and I'm supposed to move them into separate branches each. I tried reverting and creating new branches but it got messed up and I'm back at square 1. In this answer, I will assume that your branch is called feature , and that feature has the three commits in question as its three most recent commits. Create a new branch from feature : git checkout -b onecommit Nuke the two

What is git request-pull and how does it compare to making a pull request , e.g. on github ? 1. How is it supposed to be used? 2. Can it be used as replacement for pull requests (e.g. on github)? 3. What are the advantages of using it? The git request-pull command predates hosting services. As noted in comments, it's meant for a workflow that tends to include running git format-patch and git send-email to pass patches around via email. Once the patches have been tested and approved, the patch-generator might make the commits accessible on a public server that they or their company provide, and

A project I'm working on has 2 long-standing feature branches as well as the master branch. To fully automate deployments, I'd like to create a pull request from master into those two feature branches anytime a deployment goes out from a VSTS Release. What kind of tooling in VSTS would allow me to do create pull requests as a release task? You can create the Pull Request through Pull Request REST API during the release. There is Invoke HTTP REST API task but may not good for your requirement. The simple way is that you can do it through PowerShell task : Select the phase (e.g. Run on agent)

I've cloned a repo (made sure to mark the original repo as upstream ) and went the gitflow way: create a develop branch from which all new features are created and commited back to. Every push to Master from develop is by definition a release, meaning master is always deployable. I like this setup a lot. Now sometimes aside from this flow I may want to contribute back to upstream some feature that I keep in separate feature-branches. However since a feature-branch is created from develop HEAD and develop may have already had other feature-branches merged back into, this gives a problem: