account-and-team-context

Establishing whose account this is and what it reaches

Answer two questions before anything that depends on identity: who is acting, and what that account can actually see or change.

Sequence

1. Resolve the acting account. get_me returns the authenticated user. Its login is the value every later question is asked in terms of — "my pull requests", "issues assigned to me", "repositories I can push to" all mean that login.
2. Resolve organisation membership with get_teams. Called with no argument it returns the teams the authenticated account belongs to; pass user to ask the same about someone else, which only works for organisations the current credentials can already see.
3. Expand a team into people with get_team_members, using the organisation as org and the team's team_slug. The slug is the hyphenated form from the team's address, not its display name.
4. Establish repository access with list_repository_collaborators. Use affiliation to separate the populations: direct for people granted access on the repository itself, outside for collaborators who are not organisation members, and all for the combined view. The distinction matters because all includes people whose access comes from a team, who are invisible under direct.
5. Resolve a name to an account with search_users when you have a person and need their login. Qualify the query — a bare personal name matches widely.
6. Say what you established, and what you could not. An account's view of GitHub is bounded by its credentials, and a report that does not say so reads as complete.

Decision points

• "Me" is not a guess. Any request phrased in the first person — my issues, my reviews, repositories I maintain — depends on login. Resolve it rather than inferring it from a repository owner or from earlier conversation.
• Membership is not permission. Being on a team says nothing on its own about a given repository; the team may have no grant there. Check access where access matters.
• Absence is ambiguous. A team or organisation missing from get_teams may not exist, or may simply be invisible to these credentials. Both are limited to organisations the current credentials reach, and neither can tell you which case you are in.
• Names are not identities. Display names collide and change; login does not. When a request names a person, resolve to a login before acting on it, and say which account you resolved to.