github: add a note about GitHub user ids - #2331
Conversation
✅ Deploy Preview for pomerium-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Greptile SummaryAdds GitHub user-ID guidance for Pomerium 0.34.
Confidence Score: 4/5The lookup command should be made failure-sensitive before merging so administrators cannot mistake GitHub error responses lack Files Needing Attention: content/docs/integrations/user-identity/github.mdx
|
| Filename | Overview |
|---|---|
| content/docs/integrations/user-identity/github.mdx | Documents the GitHub user-ID transition, but the supplied lookup command silently emits null for error responses. |
Reviews (1): Last reviewed commit: "add a note about GitHub user ids" | Re-trigger Greptile
| To find a user's `node_id`, query the GitHub API: | ||
|
|
||
| ```bash | ||
| curl -s https://api.github.com/users/USER_LOGIN | jq -r .node_id |
There was a problem hiding this comment.
Error responses become
null IDs
When GitHub returns an error for an invalid login or failed request, this pipeline exits successfully and prints null, causing administrators to configure a user criterion that never matches. Red test: output="$(printf '%s\n' '{"message":"Not Found"}' | jq -r .node_id)"; test "$output" != null fails because the current jq expression accepts a missing field.
| curl -s https://api.github.com/users/USER_LOGIN | jq -r .node_id | |
| curl -fsS https://api.github.com/users/USER_LOGIN | jq -er .node_id |
Context Used: For every finding, write a red test with proof and... (source)
Summary
Add a note about
node_idbeing used asuser_idfor GitHub.Related
AI disclosure
none
Checklist