Add support for GitHub Gists

[pcgeek86]

We need to add operations for GitHub Gist code snippets.

Gists

https://developer.github.com/v3/gists/

• List out all Gists for the authenticated user
• List starred Gists for the authenticated user
• Star/unstar Gists
• List out all public Gists for a specific GitHub user
• Get a specific Gist
• Create a new Gist
• Delete a Gist

[dotps1]

I have a good portion of this done now. but I cannot edit your orginal check list.

still have to do:

• Set-GitHubGist which will encompass the Star/unstar.
• Delete Gist

additions:

• Get a specific revision of a gist, now that I have the Gist object Model inplace, this should be easy(ier).
• add Copy-GitHubGist cmdlet, with an alias of Fork-GitHubGist.

all I can think of, to tired.

[pcgeek86]

This is handled by #20 and #17.

[pcgeek86]

@dotps1 Please review the completed tasks for accuracy. Are all of those checked off scenarios supported? If we could write Pester tests for this as well, that would be helpful, but not a requirement for now.

[dotps1]

lol, I forgot I already did the Remove-GitHubGist cmdlet, yesterday was a long day. I am going to tackle the rest of this today/tomorrow.

Ill get to pesters too.

One thing, you should look at my WinSCP module, and check out how I laid folder structure. I just think its a little cleaner, and it gets the appveyor.yml and the tests out of the root of the module. and all the git releated stuff as well.
just a thought.

[pcgeek86]

@dotps1 The appveyor.yml is in the root of your folder in the WinSCP module. Did I misunderstand something?

[dotps1]

the easiest explanation would be to look at the repo. it just makes the deployment process easer, because only deliverable code exists in the root of the module. Basically there is a sub folder in the Repo where the deliverable(s) live. (Maybe we should move this to a new thread or we can just talk offline as well.)

Thanks.

[CollinChaffin]

So I'm confused since it looks like @dotps1 wrote all the Gist stuff back in 2016 (looking at his repo), and then worked to incorporate it here, yet after these years I'm wondering why basics like supporting shouldprocess is in his old 2016 repo copy, yet despite the rest of the code being line for line identical is missing in this maintained version. I can't believe that's by design but thought I'd ask if there are plans to add that, and perhaps the html-based help back in to this newer version? TIA!