Adding the id of the gist id to the URI makes it impossible, in practical terms, because that id is a very large random number. This is, unfortunately, a breaking change but one that cannot be avoided because of the security implications of the current URIs. We apologize for the inconvenience.

For your convenience we have also added a`comments_url` member to the Gist representations. The`comments_url` link provides access to the comments of a Gist in way that is resilient to changes in the URI patterns used by the GitHub API. We are increasing our use of links in order to make changes such as this one less damaging to clients. We strongly encourage using`url` and`*_url` properties, where possible, rather than constructing URIsbased onthe patternspublish on this site. Doing so will result it clients that break less often.

For your convenience we have also added a`comments_url` member to the Gist representations. The`comments_url` link provides access to the comments of a Gist in way that is resilient to changes in the URI patterns used by the GitHub API. We are increasing our use of links in order to make changes such as this one less damaging to clients. We strongly encourage using`url` and`*_url` properties, where possible, rather than constructing URIsusingthe patternspublished on this site. Doing so will result it clients that break less often.