188 captures

16 Aug 2013 - 29 Jan 2026

Jan	FEB	Mar
	09
2015	2016	2017

success

fail

About this capture

COLLECTED BY

Organization: Internet Archive

The Internet Archive discovers and captures web pages through many different web crawls. At any given time several distinct crawls are running, some for months, and some every day or longer. View the web archive through the Wayback Machine.

Collection: Survey Crawl Number 4 - Started Jan 9th, 2016 - Ended Feb 25th, 2016

The seed for this crawl was a list of every host in the Wayback Machine

This crawl was run at a level 1 (URLs including their embeds, plus the URLs of all outbound links including their embeds)

The WARC files associated with this crawl are not currently available to the general public.

TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20160209181149/https://help.github.com/articles/checking-out-pull-requests-locally/

GitHub Help

●

Checking out pull requests locally

● mac ● windows ● linux ● all When someone sends you a pull request from a fork or branch of your repository, you may want to merge it locally to resolve a merge conflict or to test and verify the changes on your local computer before merging on GitHub.

Modifying an active pull request locally

Under your repository name, click Pull requests. Issues and pull requests tab selection

In the "Pull Requests" list, click the pull request you'd like to merge. (三)At the bottom of the pull request, click command line. Follow the sequence of steps to bring down the proposed pull request. Show command line pull request instructions

Show command line pull request instructions

Modifying an inactive pull request locally

An inactive pull request is one whose owner has either stopped responding, or, more likely, has deleted their fork. If a fork was deleted, the pull request can still be merged. However, if you want to make changes to a pull request and the author is not responding, you'll need to perform some additional steps to update the pull request. Once a pull request is opened, GitHub stores all of the changes online for you. In other words, commits in a pull request are available in a repository even before the PR is merged. That means you can fetch an open pull request and recreate it as your own. Anyone can work with a previously opened pull request to continue working on it, test it out, or even open a new pull request with additional changes. However, only collaborators with push access can merge pull requests. Under your repository name, click Issuesor Pull requests. Issues and pull requests tab selection

In the "Pull Requests" list, click the pull request you'd like to merge. (三)Find the ID number of the inactive pull request. This is the sequence of digits right after the pull request's title. Pull Requests ID number

Open Terminal (for Mac and Linux users) or the command prompt (for Windows users). Fetch the reference to the pull request based on its ID number, creating a new branch in the process.

git fetch origin pull/ID/head:BRANCHNAME

Switch to the new branch that's based on this pull request:

[master] $ git checkout BRANCHNAME
Switched to a new branch 'BRANCHNAME'

At this point, you can do anything you want with this branch. You can run some local tests, or merge other branches into it, including master. Make modifications as you see fit! When you're ready, you can push the new branch up:

[pull-inactive-pull-request] $ git push origin BRANCHNAME
Counting objects: 32, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (26/26), done.
Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
Total 29 (delta 8), reused 0 (delta 0)
To https://github.com/username/repository.git
 * [new branch]      BRANCHNAME -> BRANCHNAME

Create a new pull request with your new branch.

Tips

The remote refs/pull/ namespace is read-only. If you try to push any commits there, you'll see this error:

! [remote rejected] HEAD -> refs/pull/1/head (deny updating a hidden ref)
error: failed to push some refs to 'git@github.local:USERNAME/REPOSITORY.git'

When you remove or rename a remote reference, your local refs/pull/origin/ namespace will not be affected by calls to git-remote. ● Contact a human

Article versions

●GitHub.com ● GitHub Enterprise 2.5 ● GitHub Enterprise 2.4 ● GitHub Enterprise 2.3 ● GitHub Enterprise 2.2 ● GitHub Enterprise 2.1 © 2016 GitHub Inc. All rights reserved. ●Terms of Service ●Privacy ●Security ●Support