Similar to #2534 and #2669.
There are many event type specific fields included in audit log events returned by the API that are not included in AuditEntry.
These are the ones that I've noticed are missing, though there might be more than these as well.
actor_ip - IP of actor (if enabled in GitHub audit logs)
actor_location - location of actor (country code etc)
hashed_token - hashed token identifier when an action is performed using an access token
job_workflow_ref - reference to workflow job when a workflow runs
oauth_application_id - OAuth application identifier when an OAuth application performs an action
org_id - organization numeric ID
programmatic_access_type - type of programmatic access (i.e. via token, cli, oauth app...)
pull_request_id - self-explanatory
pull_request_title - self-explanatory
pull_request_url - self-explanatory
reasons - Used when a user overrides branch protection, includes info on user's stated reason why
run_number - the numerical ID of the workflow run
token_id - token ID when an action is performed using an access token
token_scopes - string containing scopes assigned to a token
topic - topic used in workflow runs
user_agent - user-agent used in performing an action
Similar to #2534 and #2669.
There are many event type specific fields included in audit log events returned by the API that are not included in
AuditEntry.These are the ones that I've noticed are missing, though there might be more than these as well.
actor_ip- IP of actor (if enabled in GitHub audit logs)actor_location- location of actor (country code etc)hashed_token- hashed token identifier when an action is performed using an access tokenjob_workflow_ref- reference to workflow job when a workflow runsoauth_application_id- OAuth application identifier when an OAuth application performs an actionorg_id- organization numeric IDprogrammatic_access_type- type of programmatic access (i.e. via token, cli, oauth app...)pull_request_id- self-explanatorypull_request_title- self-explanatorypull_request_url- self-explanatoryreasons- Used when a user overrides branch protection, includes info on user's stated reason whyrun_number- the numerical ID of the workflow runtoken_id- token ID when an action is performed using an access tokentoken_scopes- string containing scopes assigned to a tokentopic- topic used in workflow runsuser_agent- user-agent used in performing an action