Down to the Wire

Lists can be turned into task lists by prefacing list items with [ ] or [x](incomplete or complete, respectively). - [x] @mentions, #refs, [links](), **formatting**, and tags are supported -...

Task lists can be nested to better structure your tasks: - [ ] a bigger project - [ ] first subtask #1234 - [ ] follow up subtask #4321 -...

Certain references are auto-linked: - SHA: a5c3785ed8d6a35868bc169f07e40e889087fd2e - User@SHA: jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e - User/Repository@SHA: jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e - #Num: #26 - GH-Num: GH-26 - User#Num: jlord#26 - User/Repository#Num: jlord/sheetsee.js#26

Comments are stored in GitHub as issues not pull requests. This comment thread is stored here: https://github.com/wireddown/ghpages-ghcomments/issues/5

Thanks for the ideas :-)

Attempt to post a comment.

Yes! I can, but likely in the first week of October.

# Stale links > Under https://github.com/settings/apps/ GitHub appears to have renamed some pages and portals. The [setup page](http://downtothewire.io/ghpages-ghcomments/setup/) asks you to visit https://github.com/settings/applications (not `apps`), but using the newer GitHub...

# Red error message Watching your blog page load, the error message in the red `` appears when [**gpgc** searches GitHub for an issue in your blog repository with the...

The situation might not be so dire :-) It looks like GitHub has tuned their `scope` access levels. Previously, [`public_repo` was sufficient](https://github.com/wireddown/ghpages-ghcomments/blob/release/public/js/gpgc_core.js#L223) to search for and comment on issues on...