This section provides an overview of what github is, and why a developer might want to use it.
It should also mention any large subjects within github, and link out to the related topics. Since the Documentation for github is new, you may need to create initial versions of those related topics.
Gists are a great way to share your work. You can share single files, parts of files, or full applications.
There are two types of gists: public gists and secret gists. Additionally, if you are not logged into GitHub when you create your gist, it will be an anonymous gist.
Public Gists
Public gists show up in Discover, where people can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work.
Secret Gists
Secret gists don't show up in Discover and are not searchable. Use them to jot down an idea that came to you in a dream, create a to-do list, or prepare some code or prose that's not ready to be shared with the world.
You can create as many secret gists as you like.
Anonymous Gists
If you create a gist without logging into GitHub, it will be an anonymous gist. Anonymous gists can be public or secret. To delete an anonymous gist on GitHub.com or GitHub Enterprise, contact GitHub support or your site administrator, respectively. Please provide the URL of the gist you wish to delete.
Tell your collaborators to rebase, not merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging.
After some time has passed and you're confident that git filter-branch had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer):
git for-each-ref --format='delete %(refname)' refs/original | git update-ref --stdin
git reflog expire --expire=now --all
git gc --prune=now
Credits:
