In the meantime, the go-github SDK removed the (classic) projects API: https://github.com/google/go-github/releases/tag/v68.0.0

So maybe this could be removed entirely now?

@0x46616c6b the intention here is/was to deprecate before removal as should have happened when the API was originally deprecated. Technically they were broken before I opened #2494 and should just be removed as their presence will block upgrading the SDK; but if a release is going out before the SDK is upgraded this PR is still valid. IMHO this PR should have been prioritised as it could have gone out in v6.5.0 or v6.6.0.

@nickfloyd IMHO this should go into the codebase before the SDK is updated even if the SDK is updated and the files are removed before the next release.

@nickfloyd IMHO this should go into the codebase before the SDK is updated even if the SDK is updated and the files are removed before the next release.

Agreed. I was sketching out what transitioning to the new project endpoints in GraphQL would look like and it's going to be a fairly significant change, let alone moving to the SDK @ v76. This type of comms is way over due. Thank you for making it happen ❤️

@nickfloyd there is a REST API for projects now.

https://docs.github.com/en/rest/projects/projects?apiVersion=2022-11-28

@nickfloyd there is a REST API for projects now.

🤦 You're right. Thank you for reminding me. ❤️