Skip to content

Commit a3e84a1

Browse files
authored
Merge pull request #45025 from github/repo-sync
Repo sync
2 parents dec52ec + d5ab360 commit a3e84a1

61 files changed

Lines changed: 1695 additions & 145 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ Streaming audit log data has these benefits:
2626
* **Data continuity**. If you pause a stream, it retains a buffer for seven days, so there is no data loss for the first week. If the stream remains paused for more than seven days, it will resume from a point one week prior to the current time. If paused for three weeks or more, the stream won't retain any data and will start anew from the current timestamp.{% endif %}
2727
* **Data retention**. Keep your exported audit logs and Git events data as long as you need to.
2828

29+
You can also stream agent session activity from {% data variables.product.prodname_copilot %} to the same destination you use for other enterprise audit events. This is currently in {% data variables.release-phases.public_preview %}. See [AUTOTITLE](/enterprise-cloud@latest/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/monitor-agentic-activity#tracking-agentic-activity-in-your-enterprise-through-the-audit-log) in the {% data variables.product.prodname_ghe_cloud %} documentation.
30+
2931
You can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports audit and Git events data for all of the organizations in your enterprise, for activity from the time the stream is enabled onwards.
3032

3133
All streamed audit logs are sent as compressed JSON files. The filename format is in`YYYY/MM/HH/MM/<uuid>.json.gz`.
@@ -57,6 +59,7 @@ To set up the audit log stream, follow the instructions for your provider:
5759
* [Azure Event Hubs](#setting-up-streaming-to-azure-event-hubs)
5860
* [Datadog](#setting-up-streaming-to-datadog)
5961
* [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
62+
* [Microsoft Purview](#setting-up-streaming-to-microsoft-purview) (Copilot agent session events only)
6063
* [Splunk](#setting-up-streaming-to-splunk)
6164

6265
{% ifversion ghec %}
@@ -265,6 +268,20 @@ To set up streaming to Google Cloud Storage, create a service account in Google
265268
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
266269
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
267270

271+
### Setting up streaming to Microsoft Purview
272+
273+
{% data reusables.copilot.agent-session-streaming-availability-note %}
274+
275+
Microsoft Purview only supports streaming {% data variables.product.prodname_copilot_short %} agent session events. For more information on Microsoft Purview, see [Learn about the Microsoft Purview portal](https://learn.microsoft.com/en-us/purview/purview-portal) in the Microsoft documentation.
276+
277+
To set up streaming to Microsoft Purview, configure streaming in {% data variables.product.github %}, then authorize access through Microsoft Entra.
278+
279+
1. Configure streaming in {% data variables.product.github %}. See [Enabling audit log streaming of {% data variables.product.prodname_copilot_short %} agent session events](#enabling-audit-log-streaming-of-copilot-agent-session-events) below.
280+
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
281+
1. Select the **Configure stream** dropdown and click **Microsoft Purview**.
282+
1. Click **Authorize with Entra**.
283+
1. When you're redirected to Microsoft Entra, add the {% data variables.product.github %} app and authorize it for your tenant.
284+
268285
### Setting up streaming to Splunk
269286

270287
To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint, make sure that the endpoint is configured to accept HTTPS connections. See [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
@@ -328,3 +345,20 @@ To restart streaming, click **Resume stream**.
328345
1. Click **Save**.
329346

330347
{% endif %}
348+
349+
{% ifversion ghec %}
350+
351+
## Enabling audit log streaming of {% data variables.product.prodname_copilot_short %} agent session events
352+
353+
{% data reusables.copilot.agent-session-streaming-availability-note %}
354+
355+
{% data reusables.enterprise-accounts.access-enterprise %}
356+
1. At the top of the page, click AI Controls
357+
1. Under "Copilot", select **Enabled everywhere** for "Copilot Usage Records Streaming"
358+
1. Configure a streaming destination. See [Setting up audit log streaming](#setting-up-audit-log-streaming).
359+
360+
You can also retrieve {% data variables.product.prodname_copilot_short %} usage data through the REST API by selecting **Enabled everywhere** for "Copilot Usage Records API". See [AUTOTITLE](/rest/copilot/copilot-usage-metrics#get-copilot-usage-records-for-an-enterprise).
361+
362+
For help interpreting the audit log events for agentic activity, see [AUTOTITLE](/copilot/reference/agentic-audit-log-events#streaming-audit-log-events).
363+
364+
{% endif %}

content/copilot/concepts/agents/about-agent-skills.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,6 @@ You can also use `gh skill` in {% data variables.product.prodname_cli %} to disc
2727
* Project skills, stored in your repository (`.github/skills`, `.claude/skills`, or `.agents/skills`)
2828
* Personal skills, stored in your home directory and shared across projects (`~/.copilot/skills` or `~/.agents/skills`)
2929

30-
Support for organization-level and enterprise-level skills is coming soon.
31-
3230
## Next steps
3331

3432
To create or add agent skills, see:

content/copilot/concepts/agents/enterprise-management.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,8 @@ An agent session encompasses an entire interaction with {% data variables.copilo
4444

4545
Enterprise administrators can use AI Controls to view active and recent agent sessions, track audit log events, and search agentic activity in your enterprise using filters. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/monitor-agentic-activity) and [AUTOTITLE](/copilot/reference/agent-session-filters).
4646

47+
For long-term retention and analysis, you can stream enterprise audit log data to supported destinations. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise) and [AUTOTITLE](/copilot/reference/agentic-audit-log-events).
48+
4749
For billing information on agent sessions, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-premium-requests#usage-by-copilot-cloud-agent).
4850

4951
## Third-party agents

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/monitor-agentic-activity.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,18 @@ category:
1919

2020
## Tracking agentic activity in your enterprise through the audit log
2121

22+
Track agentic activity on {% data variables.product.github %} or through streaming to an external destination.
23+
24+
### Viewing agentic activity in the audit log on {% data variables.product.github %}
25+
2226
{% data reusables.enterprise-accounts.access-enterprise %}
2327
{% data reusables.enterprise-accounts.ai-controls-tab %}
24-
1. To see a list of agentic activity in your enterprise over the last 180 days, at the bottom of the page, click {% octicon "log" aria-hidden="true" aria-label="log" %} **Audit logs**.
28+
1. At the bottom of the page, click {% octicon "log" aria-hidden="true" aria-label="log" %} **Audit logs**.
29+
30+
### Streaming agentic activity from the audit log
31+
32+
{% data reusables.copilot.agent-session-streaming-availability-note %}
33+
34+
To enable streaming for {% data variables.product.prodname_copilot_short %} agent session events and configure a streaming destination from your enterprise audit log settings, see [AUTOTITLE](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise#enabling-audit-log-streaming-of-copilot-agent-session-events).
2535

26-
For help interpreting the audit log events for agentic activity, see [AUTOTITLE](/copilot/reference/agentic-audit-log-events).
36+
In addition to streaming, you can also retrieve Copilot usage data through the REST API. See [AUTOTITLE](/rest/copilot/copilot-usage-metrics#get-copilot-usage-records-for-an-enterprise).

content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,20 @@ To add a specific file to your prompt, use `@` followed by the relative path to
9595

9696
When you start typing a file path, the matching paths are displayed below the prompt box. Use the arrow keys to select a path and press <kbd>Tab</kbd> to complete the path in your prompt.
9797

98+
### Attach images and PDFs
99+
100+
You can attach images and PDFs to your prompts when using a model that supports image input.
101+
102+
{% data reusables.copilot.supported-attachment-file-types %}
103+
104+
{% data reusables.copilot.image-pdf-attachment-handling %}
105+
106+
You can attach a file in the following ways during an interactive session:
107+
108+
* Reference the file in your prompt using `@` followed by the path to the file.
109+
* Drag and drop a file into the interactive session.
110+
* Copy an image to your clipboard, then paste it as an attachment.
111+
98112
### Work with files in a different location
99113

100114
To complete a task, {% data variables.product.prodname_copilot_short %} may need to work with files that are outside the current working directory. If a prompt you have entered in an interactive session requires {% data variables.product.prodname_copilot_short %} to modify a file outside the current location, it will ask you to approve access to the file's directory.

content/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ The response to your edited question is displayed in a new subthread. An edit co
6868

6969
### Using images in {% data variables.copilot.copilot_chat_short %}
7070

71-
> [!NOTE] This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
71+
{% data reusables.copilot.using-images-in-chat %}
7272

73-
You can attach images to your prompts by pasting, dragging, or clicking {% octicon "plus" aria-label="Add attachment" %} in the prompt box and then selecting **{% octicon "file-code" aria-hidden="true" %} Upload from computer**. Select a model that supports images from the model picker. For supported file types and example questions, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/provide-visual-inputs).
73+
To attach a file, drag and drop it into the prompt box, or click {% octicon "plus" aria-label="Add attachment" %} and select **{% octicon "file-code" aria-hidden="true" %} Upload from computer**. Select a model that supports image input from the model picker.
7474

7575
### Continuing a conversation alongside an agent session
7676

content/copilot/reference/agentic-audit-log-events.md

Lines changed: 23 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,33 @@ category:
1010
- Learn about Copilot
1111
---
1212

13-
You can apply the `actor:Copilot` filter to your enterprise audit log to view agentic activity over the last 180 days. The following key fields can help you interpret agentic events:
13+
You can apply the `actor:Copilot` filter to your enterprise audit log to view agentic activity over the last 180 days.
14+
15+
The following key fields can help you interpret agentic events:
1416

1517
| Field | Description | Example value |
1618
| --- | --- | --- |
1719
| `action` | The action performed by the agent, such as creating a pull request. | `pull_request.create` |
1820
| `actor_is_agent` | Indicates whether the actor is an AI agent. This will always be `true` for agentic audit log events. | `true` |
1921
| `agent_session_id` | A unique identifier linking to the specific agent session that generated the event. This field only appears when the event is the result of an agent session. | `012345a6-b7c8-9012-de3f-45gh678i9012` |
2022
| `user` | The person who initiated the agentic event. | `octocat` |
23+
24+
## Streaming audit log events
25+
26+
{% data reusables.copilot.agent-session-streaming-availability-note %}
27+
28+
The table below shows the fields that are included in each streamed {% data variables.product.prodname_copilot_short %} API usage record.
29+
30+
Each streamed record is a JSON object with the following properties:
31+
32+
| Field | Type | Description |
33+
| --- | --- | --- |
34+
| `type` | `string` | The record type (`request` or `response`). |
35+
| `user_id` | `integer` | The ID of the user who made the request. |
36+
| `enterprise_id` | `integer` | The ID of the enterprise. |
37+
| `endpoint` | `string` | The {% data variables.product.prodname_copilot_short %} API endpoint the usage record interacted with. |
38+
| `body` | `string` | The request or response body (JSON-encoded string). |
39+
| `@timestamp` | `integer` | Milliseconds since Unix epoch. |
40+
| `truncated` | `boolean` | `true` when the `body` field has been trimmed to fit within the 1 MB document size limit. Omitted (treated as `false`) when the body is delivered in full. |
41+
| `event_id` | `string` | Unique event identifier for this streamed usage record. |
42+
| `github_request_id` | `string` | {% data variables.product.github %} request identifier associated with the {% data variables.product.prodname_copilot_short %} usage event. |

content/issues/planning-and-tracking-with-projects/understanding-fields/about-issue-fields.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,6 @@ category:
99
- Manage project items and fields
1010
---
1111

12-
{% data reusables.issues.issue-fields-public-preview-note %}
13-
1412
Issue fields are organization-level fields that provide consistent, typed metadata across all repositories. Unlike project custom fields, issue fields are defined once at the organization level and are available on every issue and in every project across the organization. For more information on creating and managing issue fields, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-fields-in-your-organization).
1513

1614
## Issue fields in public and internal projects

content/issues/tracking-your-work-with-issues/using-issues/adding-and-managing-issue-fields.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ category:
1010
- Create and work with issues
1111
---
1212

13-
{% data reusables.issues.issue-fields-public-preview-note %}
14-
1513
Issue fields appear in the right-hand sidebar of issues, alongside system fields like assignees, labels, and type. You can set values when creating or editing an issue. When you select an issue type while creating an issue, any fields pinned to that type automatically appear in the sidebar.
1614

1715
> [!NOTE]

content/issues/tracking-your-work-with-issues/using-issues/managing-issue-fields-in-your-organization.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ category:
1212
- Triage and organize issues
1313
---
1414

15-
{% data reusables.issues.issue-fields-public-preview-note %}
16-
1715
Issue fields let you add structured metadata to issues across your organization. Instead of relying on labels or free-text workarounds, you can create fields like priority, effort, impact, or any custom category your team needs. Fields are defined at the organization level and apply across all repositories in your organization.
1816

1917
## About issue field types

0 commit comments

Comments
 (0)