How Do I Edit or Delete a Gist? In the top right corner of your gist page, there will be a menu that allows for multiple functions to be performed on your gist. We can edit, delete, unsubscribe, star, embed, copy, share, and download a raw copy or zipped copy of a gist. We also can share a gist in multiple ways.
Gist: Is an additional feature added to github to allow the sharing of code snippets, notes, to do lists and more. You can save your Gists as secret or public. Secret Gists are hidden from search engines but visible to anyone you share the url with.
Gists let you share code snippets, entire files, or even applications. You can also use gists to save and share console output when running, debugging, or testing your code. Each gist is a repository that can be cloned or forked by other people.
Even better, you can add a file with a leading space in its name. It's virtually invisible and gives you more freedom when choosing the title and names for the files:
Considering the order of files within a gist is asciibetical, you can try and add one file in uppercase.
That file will come before any other and will define the name of your gist.
Note that it won't change the url of said gist, as explained in "Namespaced Gists".
Currently, there's no way rename a Github gist. There's been an open issue on this. I would suggest you add a text file to your gist. The file name should start with space (
), a hash sign (#
), an exclamation mark (!
), a dollar sign ($
) or an ampersand (&
). You can add a long description to the body.
For example, naming your file #Github Tricks
will change your gist title to #Github Tricks
. This will also work if your file name starts with a space (
) like Github Tricks
. If both files exist, the title starting with space takes precedence.
The file names in your gist determine the gist title. The order is listed below.
\t
, \n
, \x0b
, \x0c
, \r
,
, !
, "
, #
, $
, %
, &
, \'
, (
, )
, *
, +
, ,
, -
, .
, /
, 0
, 1
, 2
, 3
, 4
, 5
, 6
, 7
, 8
, 9
, :
, ;
, <
, =
, >
, ?
, @
, A
, B
, C
, D
, E
, F
, G
, H
, I
, J
, K
, L
, M
, N
, O
, P
, Q
, R
, S
, T
, U
, V
, W
, X
, Y
, Z
, [
, \\
, ]
, ^
, _
, `
, a
, b
, c
, d
, e
, f
, g
, h
, i
, j
, k
, l
, m
, n
, o
, p
, q
, r
, s
, t
, u
, v
, w
, x
, y
, z
, {
, |
, }
, ~
What I do is creating a first file with leading underscore example : '_simple gist.md' and set it's type as markdown so it also serves as description of my gist .. after reading this post, I will prefix a leading space.
An even better way is to use an ! (exclamation) in front of the name of the file that you always want to be the first in the order. That way you avoid having to add a space everytime you edit the file, as well as adding a tilde ~ to all the remaining files which can be an arbitrary long list.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With