33 lines
1.2 KiB
Markdown
33 lines
1.2 KiB
Markdown
---
|
|
title: Forking and cloning gists
|
|
intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.'
|
|
redirect_from:
|
|
- /articles/forking-and-cloning-gists
|
|
versions:
|
|
free-pro-team: '*'
|
|
enterprise-server: '*'
|
|
github-ae: '*'
|
|
---
|
|
|
|
### Forking gists
|
|
|
|
Each gist indicates which forks have activity, making it easy to find interesting changes from coworkers or complete strangers.
|
|
|
|
|
|
|
|
### Cloning gists
|
|
|
|
If you want to make local changes to a gist and push them up to the web, you can clone a gist and make commits the same as you would with any Git repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
|
|
|
|
|
|
|
|
### Viewing gist commit history
|
|
|
|
To view a gist's full commit history, click the "Revisions" tab at the top of the gist{.
|
|
|
|
|
|
|
|
You will see a full commit history for the gist with diffs.
|
|
|
|
|