Triggered when you create a listing for your app in GitHub Marketplace. Triggered when your listing is approved for inclusion in GitHub Marketplace. Marketplace_listing category actions Action Triggered when you sign the GitHub Marketplace Developer Agreement.
Marketplace_agreement_signature category actions Action Triggered when you change your personal account's access and security setting for Codespaces.
#I see password review trail update
Triggered when you update the repositories a codespace has access to. Triggered when you resume a suspended codespace. Triggered when you change your email address. Triggered when you change how you pay for GitHub. Keyġ429548104000 (Timestamp shows the time since Epoch with "issue_comment", "pull_request", "pull_request_review_comment"]Īn overview of some of the most common actions that are recorded as events in the security log. QualifierĪfter you export the log, you'll see the following keys and values in the resulting file. To filter the results in your export, search by one or more of these supported qualifiers before using the Export drop-down menu. You can export the log as JSON data or a comma-separated value (CSV) file. For more information, see " About Codespaces."Ĭontains all activities related to signing the GitHub Marketplace Developer Agreement.Ĭontains all activities related to listing apps in GitHub Marketplace.Ĭontains all activities related to OAuth Apps you've connected with.Ĭontains all activities related to paying for your GitHub subscription.Ĭontains all activities related to your profile picture.Ĭontains all activities related to project boards.Ĭontains all activities related to your public SSH keys.Ĭontains all activities related to the repositories you own.Ĭontains all events related to GitHub Sponsors and sponsor buttons (see " About GitHub Sponsors" and " Displaying a sponsor button in your repository")Ĭontains all activities related to two-factor authentication.Ĭontains all activities related to your account. Actions are grouped into the following categories: Category nameĬontains all activities related to your billing information.Ĭontains all activities related to GitHub Codespaces. The events listed in your security log are triggered by your actions. Note that you can only use a GitHub username, not an individual's real name. -actor:hubot excludes all events performed by hubot.actor:octocat actor:hubot finds all events performed by both octocat and hubot.actor:octocat finds all events performed by octocat.The actor qualifier can scope events based on who performed the action. Note that you must include the account name within the repo qualifier searching for just repo:our-repo will not work. -repo:my-org/not-this-repo excludes all events that occurred for the not-this-repo repository in the my-org organization.repo:my-org/our-repo repo:my-org/another-repo finds all events that occurred for both the our-repo and another-repo repositories in the my-org organization.repo:my-org/our-repo finds all events that occurred for the our-repo repository in the my-org organization.Use the repo qualifier to limit actions to a specific repository. operation:transfer finds all events where an existing resource was transferred.operation:restore finds all events where an existing resource was restored.operation:remove finds all events where an existing resource was removed.operation:modify finds all events where an existing resource was modified.operation:create finds all events where a resource was created.operation:authentication finds all events where an authentication event was performed.operation:access finds all events where a resource was accessed.Use the operation qualifier to limit actions to specific types of operations. For more information, see " Searching on GitHub." Search based on operation Many operators used when querying the log, such as -, >, or <, match the same format as searching across GitHub. You can, however, construct search queries using a variety of filters. Note that you cannot search for entries using text. Which repository an action was performed in.The user (actor) who performed the action.The organization an action was performed in.For example, the repo.create entry refers to the create operation on the repo category.Įach audit log entry shows applicable information about an event, such as: The name for each audit log entry is composed of the action object or category qualifier, followed by an operation type. In the "Archives" section of the sidebar, click Security log.
In the upper-right corner of any page, click your profile photo, then click Settings. The security log lists all actions performed within the last 90 days.
0 kommentar(er)
