How to quickly receive a transfer request

Question

Before merging the transfer request, I want to quickly execute the request locally and run tests and test several materials. I do not want to delete the gihub port request.

I thought a pulley would help http://ejohn.org/blog/pulley/ . But I get an error

$ node pulley.js 76 node.js:116 throw e; // process.nextTick error, or 'error' event on first tick ^ 

Is there any other tool that will help me quickly pull out a pull request?

Answer 1

Click on (i) on the left side of the “merge request” panel, it will provide you with the commands you need.

_________________________________________________________ ^^^^^^^^^^^^^^

Answer 2

Why not just use the following?

 git remote add -f <test_repo_name> <test_repo_url> git checkout -b <branch> <test_repo_name>/master ...test as needed ...merge if you like it 

Answer 3

Taken from the official github page (in July 2013, but this may change):

Step 1: Open a new branch to check for changes - run this from the project directory

 git checkout -b otherrepo-develop develop 

Step 2: Bring changes and test to another place (where commits take place)

 git pull git://github.com/otherrepoauthor/otherrepo.git develop 

Step 3: AFTER A SUCCESSFUL TEST! Merge Changes and Server Update

 git checkout develop git merge otherrepo-develop git push origin develop 

Answer 4

Just a quick idea, why not create a local branch and then do the stretching on the original (remotely tracked) branch?

Answer 5

It looks like you are looking for the fetch command

git-fetch

Selects names or tags from one or more other repositories along with the objects needed to complete them.

Link names and their object names from the extracted links are stored in .git / FETCH_HEAD. This information remains for the subsequent merge operation performed with git merge.

In practice, fetch gets all named commits from a remote repository. This means that when you go to the original incident, the source / master will be updated to indicate the last change in origin, but your local master will not be merged or changed to reflect these changes.

I assume that you are working on a (local) master, which is a remote branch of origin / master tracking. Your branch names may differ, but the process is the same.

Now you can create a temp branch to perform start / wizard checks by doing

 git checkout -b temp_branch_name origin/master 

which will create a temp branch that now points to the latest history in the remote repository.

When you finish testing and want to integrate, you can either do

 git checkout master git merge origin/master 

which will perform normal merging (as pull would be done) or

 git checkout master git rebase origin/master 

if you prefer to reinstall your changes to get a linear history.

Answer 6

From google search: git-pull