-
Notifications
You must be signed in to change notification settings - Fork 65k
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/graphql/guides/using-global-node-ids
What part(s) of the article would you like to see updated?
The page says:
You can access most objects in GitHub (users, issues, pull requests, etc.) using either the REST API or the GraphQL API. With a recent update, you can find the global node ID of many objects from within the REST API and use these IDs in your GraphQL operations.
Today is 2022-May-12. That recent update isn't technically 5 years old, but it also isn't the kind of thing I should have to click to discover is not recent.
Fwiw, there is a newer GraphQL NodeID transition for which I'm hunting documentation, and while this was a high hit, it was a false positive, and it wasn't remotely obvious how bad of a false positive it was until I followed the link. It's pretty frustrating.
Additional information
A quick look through:
https://cs.github.com/?scopeName=All+repos&scope=&q=repo%3Agithub%2Fdocs+%2F%5C%5B%5B%5E%5C%5D%5D*%5C%5D%5C%28%5B%5E%29%5D*developer.github.com.changes.2%2F+NOT+path%3A%2F%5Etranslations%5C%2F%2F
(n.b. this query was not fun to construct.)
... indicates this is the only instance of this specific problem (at least for markdown links to developer.github.com/changes), although blog post feels like the equivalent of "click here". -- It'd be nicer if those other pages included the blog post titles instead of using the generic term.