The content of mannequin users' login field is inconsistent between GraphQL and REST API

[Fs00]

Hello everyone,
I'd like to point out a current limitation/inconsistency of the GitHub REST API when dealing with Mannequin users.
There is currently no way for the REST API to know which name is displayed in the web UI for a Mannequin user. See for example the user field in the response of this API call that fetches an issue opened by a mannequin:

  "user": {
    "login": "ebd80758-eb43-4a34-86bb-a2b2a2196e69",
    "id": 101761789,
    "node_id": "M_kgDOBhDC_Q",
    "avatar_url": "https://avatars.githubusercontent.com/u/101761789?v=4",
    "type": "Mannequin",
    // other fields...
  },

The name of this user displayed in the web UI is bbum. The response doesn't contain this name in any of the fields.
However, if I fetch the same issue with the GraphQL API, I get:

  "data": {
    "repository": {
      "issue": {
        "author": {
          "login": "bbum",
          "url": "https://github.com/ebd80758-eb43-4a34-86bb-a2b2a2196e69"
        },
        // other fields...
      }
    }
  }

The login field here contains the name of the user that gets displayed in the web UI, which tends to be much more useful than the randomly generated UUID when you use the API response to populate a UI screen.

So I would propose to tackle this issue in either two ways:

• change the REST API to return the display name of the mannequin in the login field, as the GraphQL API does (which is a behavior change but is unlikely to break anyone, I'd prefer it for consistency)
• add an optional mannequin_name field (or similar name) to the REST API so that at least clients can access the display name of a mannequin and use it when populating a GUI screen

Thank you! 🙏

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬