You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/code-security/how-tos/manage-security-alerts/manage-secret-scanning-alerts/monitoring-alerts.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Monitoring alerts from secret scanning
3
-
intro: Learn how and when {% data variables.product.github %} will notify you about a secret scanning alert.
3
+
intro: You can configure how {% data variables.product.prodname_secret_scanning %} notifies you about {% data variables.product.prodname_secret_scanning %} alerts, and audit how your team responds to these alerts.
4
4
permissions: '{% data reusables.permissions.secret-scanning-alerts %}'
When {% data variables.product.prodname_secret_scanning %} detects a potential secret leak in your repository, staying informed about these alerts is crucial for maintaining your code's security. {% data variables.product.github %} provides multiple notification channels to ensure you and your team are promptly alerted when secrets are found. You can customize how and when you receive these notifications based on your role and preferences.
22
+
23
+
You can also audit responses to {% data variables.product.prodname_secret_scanning %} alerts to track how your team manages security issues and maintain compliance with your organization's security policies.
24
+
21
25
## Configuring notifications for {% data variables.secret-scanning.alerts %}
22
26
23
27
In addition to displaying an alert in the **Security** tab of the repository, {% data variables.product.github %} can also send email notifications for alerts. These notifications are different for incremental scans and historical scans.
Copy file name to clipboardExpand all lines: content/copilot/how-tos/copilot-cli/cli-best-practices.md
+54-15Lines changed: 54 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,7 +199,7 @@ For best results on complex tasks:
199
199
200
200
**Session storage location:**
201
201
202
-
```copilot
202
+
```text
203
203
~/.copilot/session-state/{session-id}/
204
204
├── events.jsonl # Full session history
205
205
├── workspace.yaml # Metadata
@@ -213,17 +213,38 @@ For best results on complex tasks:
213
213
214
214
### Session management commands
215
215
216
-
```bash
217
-
# View session info
216
+
To view information about the current CLI session, enter:
217
+
218
+
```copilot
218
219
/session
220
+
```
221
+
222
+
To view a list of any session checkpoints, enter:
219
223
220
-
# View checkpoint history
224
+
```copilot
221
225
/session checkpoints
226
+
```
227
+
228
+
> [!NOTE]
229
+
> A checkpoint is created when session context is compacted, and allows you to view the summary context that {% data variables.product.prodname_copilot_short %} created.
230
+
231
+
To view the details of a specific checkpoint, enter:
222
232
223
-
# View files in session
233
+
```copilot
234
+
/session checkpoints NUMBER
235
+
```
236
+
237
+
where NUMBER specifies the checkpoint you want to display.
238
+
239
+
To view any temporary files that have been created during the current session—for example, artifacts created by {% data variables.product.prodname_copilot_short %} that shouldn't be saved to the repository—enter:
240
+
241
+
```copilot
224
242
/session files
243
+
```
244
+
245
+
To view the current plan (if {% data variables.product.prodname_copilot_short %} has generated one), enter:
225
246
226
-
# View current plan
247
+
```copilot
227
248
/session plan
228
249
```
229
250
@@ -317,7 +338,6 @@ Pair with {% data variables.copilot.copilot_cli_short %} to develop tests.
317
338
*`/plan Migrate all class components to functional components with hooks`
318
339
319
340
Then answer the questions {% data variables.product.prodname_copilot_short %} asks. Review the plan it creates, and ask {% data variables.product.prodname_copilot_short %} to make changes if necessary. When you are happy with the plan you can prompt:
320
-
321
341
`Implement this plan`
322
342
323
343
## 6. Advanced patterns
@@ -352,13 +372,13 @@ copilot
352
372
353
373
**View and manage allowed directories:**
354
374
355
-
```bash
375
+
```copilot
356
376
/list-dirs
357
377
```
358
378
359
379
**Example workflow: coordinated API changes**
360
380
361
-
```bash
381
+
```copilot
362
382
I need to update the user authentication API. The changes span:
@@ -379,7 +399,7 @@ This multi-repository capability enables:
379
399
380
400
{% data variables.product.prodname_copilot_short %} can work with visual references. Simply **drag and drop** images directly into the CLI input, or reference image files:
381
401
382
-
```bash
402
+
```copilot
383
403
Implement this design: @mockup.png
384
404
Match the layout and spacing exactly
385
405
```
@@ -388,7 +408,7 @@ Match the layout and spacing exactly
388
408
389
409
For large-scale changes:
390
410
391
-
```bash
411
+
```copilot
392
412
Run the linter and write all errors to `migration-checklist.md` as a checklist.
393
413
Then fix each issue one by one, checking them off as you go.
394
414
```
@@ -424,16 +444,35 @@ Track metrics like:
424
444
* Code review feedback cycles
425
445
* Test coverage improvements
426
446
427
-
### Getting help
447
+
## Getting help
448
+
449
+
From the command line, you can display help by using the command: `copilot -h`.
450
+
451
+
For help on various topics enter:
428
452
429
453
```bash
430
-
# In-CLI help
454
+
copilot help TOPIC
455
+
```
456
+
457
+
where `TOPIC` can be one of: `config`, `commands`, `environment`, `logging`, or `permissions`.
458
+
459
+
### Within the CLI
460
+
461
+
For help within the CLI, enter:
462
+
463
+
```copilot
431
464
/help
465
+
```
432
466
433
-
# View usage statistics
467
+
To view usage statistics, enter:
468
+
469
+
```copilot
434
470
/usage
471
+
```
435
472
436
-
# Submit feedback
473
+
To submit private feedback to {% data variables.product.github %} about {% data variables.copilot.copilot_cli_short %}, raise a bug report, or submit a feature request, enter:
intro: 'You can attach images to issues or {% data variables.copilot.copilot_chat_short %} prompts to help {% data variables.product.prodname_copilot_short %} understand your task.'
5
+
product: '{% data reusables.gated-features.copilot-coding-agent %}<br><a href="https://github.com/features/copilot/plans?ref_product=copilot&ref_type=engagement&ref_style=button" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_copilot_short %}</span> {% octicon "link-external" height:16 %}</a>'
6
+
versions:
7
+
feature: copilot
8
+
topics:
9
+
- Copilot
10
+
contentType: how-tos
11
+
category:
12
+
- Author and optimize with Copilot
13
+
---
14
+
15
+
> [!NOTE]
16
+
> For an overview of {% data variables.copilot.copilot_coding_agent %}, see [AUTOTITLE](/copilot/concepts/about-copilot-coding-agent).
17
+
18
+
## Introduction
19
+
20
+
{% data variables.copilot.copilot_coding_agent_short_cap_c %} can process images, such as a photo or screenshot of a sketch or design, as part of your task description. This is useful when you want to show {% data variables.product.prodname_copilot_short %} what you're trying to achieve visually, for example, when updating a UI or implementing a design.
21
+
22
+
You can provide images to {% data variables.product.prodname_copilot_short %} in two ways:
23
+
24
+
***In an issue**: Add an image to the issue body, with a description of the task you want {% data variables.product.prodname_copilot_short %} to complete, then assign the issue to {% data variables.product.prodname_copilot_short %}.
25
+
***In {% data variables.copilot.copilot_chat_short %}**: Attach images to your prompt when you ask {% data variables.product.prodname_copilot_short %} to create a pull request.
26
+
27
+
## Attaching images to an issue
28
+
29
+
1. Navigate to the repository where you want to create the issue.
30
+
1. Create a new issue or open an existing issue.
31
+
1. In the issue body, drag and drop your image.
32
+
1. Add a clear description of what you want {% data variables.product.prodname_copilot_short %} to do with the image. For example, "Let's update the login form to match this mockup".
33
+
1. Assign the issue to {% data variables.product.prodname_copilot_short %}. For detailed instructions, see [Assign an issue to {% data variables.product.prodname_copilot_short %} on {% data variables.product.prodname_dotcom_the_website %}](/copilot/how-tos/use-copilot-agents/coding-agent/create-a-pr#assigning-an-issue-to-copilot-on-githubcom).
34
+
35
+
{% data variables.product.prodname_copilot_short %} will analyze the image along with your description when working on the task.
36
+
37
+
## Attaching images in {% data variables.copilot.copilot_chat_short %}
38
+
39
+
1. Open {% data variables.copilot.copilot_chat_short %}.
40
+
1. Attach your image to the chat prompt, and use `/task` to describe what you want {% data variables.product.prodname_copilot_short %} to do. For example, "Update the notification badge to match this mockup".
41
+
42
+
For detailed instructions, see [Asking {% data variables.product.prodname_copilot_short %} to create a pull request from {% data variables.copilot.copilot_chat_short %} in {% data variables.product.prodname_dotcom_the_website %}](/copilot/how-tos/use-copilot-agents/coding-agent/create-a-pr#asking-copilot-to-create-a-pull-request-from-copilot-chat-in-githubcom).
43
+
1. {% data variables.product.prodname_copilot_short %} will create a pull request using the image as context for the task.
0 commit comments