There exists an undocumented way to work with API - it's possible to select repository not only with owner/repo, but also with repository_id.
I believe this should be described somewhere, since every endpoint that works with repo can be accessed this way
For example: https://github.com/_p/api/repositories/189621607 or even https://github.com/_p/api/repositories/189621607/issues
I think this way to access API is useful, since it's unaffected by any renaming and repository moving. It works and undocumented for at least several years, and even implemented in some SDK, so it's probably reasonable to explain such behavior in docs
5 years ago in this issue you've said that these endpoints are going to be documented. They still work, but there is no docs.
So, whats the plans about them?
There exists an undocumented way to work with API - it's possible to select repository not only with owner/repo, but also with repository_id.
I believe this should be described somewhere, since every endpoint that works with repo can be accessed this way
For example: https://github.com/_p/api/repositories/189621607 or even https://github.com/_p/api/repositories/189621607/issues
I think this way to access API is useful, since it's unaffected by any renaming and repository moving. It works and undocumented for at least several years, and even implemented in some SDK, so it's probably reasonable to explain such behavior in docs
5 years ago in this issue you've said that these endpoints are going to be documented. They still work, but there is no docs.
So, whats the plans about them?