Thanks for your input.

Is GraphQL the only way to read which issues are pinned? There's no REST API way to do this?

Can you explain exactly how to submit a formal feature request? Going to github.com/github/feedback redirects to the home page of this community page.

I can't see any issues in github/rest-api-description, is that a good place to open one for this feature request?

good questions ,,,let me clarify both

on REST vs GraphQL :

• no,,,REST genuinely has no way to read pinned status. ive checked the issues endpoint schema again and theres no pinned field anywhere in the rest response,,, graphql is the only option right now if you need this programmatically.specifically youd query:

repository(owner: "x", name: "y") { pinnedIssues(first: 3) { nodes { issue { number } } } }

so your backup script would need to make at least one graphql call even if the rest of your tooling is rest-based ,,, thats just the reality of the current api gap.

on the feedback link,,,my mistake there, you're right that github.com/github/feedback just redirects back to this community home now ,,,looks like that repo got folded into the commmunity discussions setup at some point and i was going off outdated info. sorry about that

the actual right path is:

• this discussion thread itself IS the formal feedback channel now,,,product feedback discussions here get reviewed by github's product teamss per the bot's auto-reply above. theres no separate submission form anymore .
• for rest-api-description,, thats really meant for documentation /spec issues (wrong descriptions ,missing fields in the openapi spec) rather than feature requests for new endpoints. so its not quite the right venue either,,,,id skip opening one there,

basically this discussion you already started is the correct venue,,,,,,,the more upvotes /comments /real use cases(like your backup tooling) it gets, the more visibility it has. no separate form needed