All Documentation

Documentation Everywhere else

Audit events: seats and work

The third page of the audit catalogue: seats and the record of the work.

Page four of five: what the room did to the record of the work — pages, pull requests, files, outcomes.

Seats, the work and its record

TypeReported byWhenDetail carries
page.publishedMac and serverA page the room built was published at a link.id, title
page.visibilityServerA page's owner shared it with anyone who has the link, or made it private again.page, visibility
file.sentMacA seat handed the person a file (send_file).bytes, uploaded, asked
pr.card.actionMacAn action was taken from a pull request's card.number, kind, ok
pr.card.hideMacA pull request was hidden from a person's list.number
pr.card.showMacA hidden pull request was shown again.number
pr.card.removeMacA pull request GitHub no longer has was removed from a discussion.number
records.reachedMacA seat's step named one of the app's own records; the run was stopped and the discussions written back.file, speaker, tool
workdir.movedMacA discussion's files were moved into an empty folder with it.discussions, entries
workdir.renamedMacWorking folder renamed.from, to, discussions
backup.keptMacA file was copied before the room changed it, in a discussion with no checkpoint.file, bytes
backup.restoredMacThe person put a kept copy back.file
approval.agedMacAn unattended run skipped an Always older than the person's limit.the rule, the days allowed
approval.unansweredMacNo answer within the person's time limit, so it was not done.id, kind, minutes
approval.skippedMacRefused unasked: an earlier approval this turn went unanswered.kind, what was asked, seat
workspace.warnedMacA workspace folder was named for what it is: home, system, app data, cloud-synced or keys.kind, whether the person went ahead
automation.notesMacAn automation's notes were replaced, by an agreed run or the person.automation, characters, who
session.temporaryMacA discussion was made temporary: not saved, synced or remembered from.nothing beyond the event
session.keptMacA temporary discussion was kept: saved and synced from then on.nothing beyond the event
background.watchMacNew lines from a watched command carried a discussion on.task, lines, lines over the limit, how it ended
repo.notes_removedMacA saved note was undone from its run's Summary.removed
github.installedServerA GitHub App installation was linked to the account that pays for its pull-request reviews.installationId, team
github.uninstalledServerA GitHub App installation was unlinked here, or removed at GitHub.installationId, by
cloud.job.startedServerA cloud job of several tasks was approved and started; its tasks' keys are minted inside its ceiling.jobId, tasks, maxParallel, delivery, mergePolicy, repo, usd
cloud.job.finishedServerA cloud job stopped running: done, failed, paused (out of time or budget) or cancelled.jobId, status, done, failed, usd
cloud.job.pr_openedServerThe GitHub App opened a pull request for a finished task of a cloud job the person gave server delivery.jobId, task, repo, number
cloud.run.pr_openedServerA cloud run started from a repository opened its work as a draft pull request (lib/cloud-repo.ts).jobId, repo, number, branch
cloud.job.pr_fixedServerThe GitHub App pushed a cloud job's fix for its pull request's failing checks onto the task's own branch (merge when green, at most two rounds per task).jobId, task, repo, number, round
cloud.job.pr_mergedServerThe GitHub App merged a cloud job's pull request: merge-when-green chosen, its checks green, the tasks it builds on merged.jobId, task, repo, number, method
pr.review.postedServerThe App reviewed a pull request: summary comment, inline comments, check.repo, number, findings, inline, standing, addressed, lookups, settled, usd, trigger
pr.review.refusedServerA pull-request review did not run, and the pull request was told why in one line.repo, number, why
pr.review.objectionServerSomeone who looks after a repository settled a review finding, so it is not raised there again.repo, path, by, how
pr.review.requestedServerSomeone asked for a pull-request review from an assistant (the MCP connector), and it was queued.repo, number, via, mode
pr.review.commandServerThe App answered a question asked in a pull request.repo, number, command, by, usd, lookups
channel.connectedServerA messaging channel was connected to the account (row 249): a Telegram bot.channel, bot
channel.disconnectedServerA messaging channel was disconnected from the account.channel
report.createdServerA report was created from a discussion.id, title
share.createdServerA discussion was shared by public link.chatId, expiresAt, forced
codrive.turnServerA co-driven turn changed hands.driver

Mac: the member's app reported it, and an admin of that Mac could suppress it. Server: our servers saw it.

Reading the pages together

Follow one discussion by chatId, one person by actor; a discussion's events run from run.started on the first page to outcome.reverted here.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.