diff --git a/CHANGELOG.md b/CHANGELOG.md index 467b1b3c39e3..86f49428b401 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,12 @@ **9 April 2026** -We have added documentation for the code security risk assessment (CSRA), a free self-serve tool that helps organization admins and security managers understand their organization's exposure to code vulnerabilities. +We've added a conceptual article to the Copilot CLI documentation explaining the context window, compaction, and checkpoints. + +[Managing context in GitHub Copilot CLI](https://docs.github.com/copilot/concepts/agents/copilot-cli/context-management) + +We've also added documentation for the code security risk assessment (CSRA), a free self-serve tool that helps organization admins and security managers understand their organization's exposure to code vulnerabilities. + New content includes: * [Code security risk assessment](https://docs.github.com/en/code-security/concepts/code-scanning/code-security-risk-assessment): What the CSRA is, who can run it, what it scans, and how it relates to the secret risk assessment. diff --git a/content/code-security/concepts/security-at-scale/about-security-overview.md b/content/code-security/concepts/security-at-scale/about-security-overview.md index c20c20697684..4b67f404c9e6 100644 --- a/content/code-security/concepts/security-at-scale/about-security-overview.md +++ b/content/code-security/concepts/security-at-scale/about-security-overview.md @@ -56,7 +56,7 @@ The views are interactive with filters that allow you to look at the aggregated {% data reusables.security-overview.download-csv-files %} For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %} -There are dedicated views for each type of security alert. You can limit your analysis to a specific type of alert, and then narrow the results further with a range of filters specific to each view. For example, in the {% data variables.product.prodname_secret_scanning %} alert view, you can use the "Secret type" filter to view only {% data variables.secret-scanning.alerts %} for a specific secret, like a {% data variables.product.prodname_dotcom %} {% data variables.product.pat_generic %}. +There are dedicated views for each type of security alert. You can limit your analysis to a specific type of alert, and then narrow the results further with a range of filters specific to each view. For example, in the {% data variables.product.prodname_secret_scanning %} view, you can use the "Secret type" filter to view only {% data variables.secret-scanning.alerts %} for a specific secret, like a {% data variables.product.prodname_dotcom %} {% data variables.product.pat_generic %}. > [!NOTE] > Security overview displays active alerts raised by security features. If there are no alerts shown in security overview for a repository, undetected security vulnerabilities or code errors may still exist or the feature may not be enabled for that repository. @@ -70,14 +70,14 @@ You can find security overview on the **{% data variables.product.prodname_secur Security overview has multiple views that provide different ways to explore enablement and alert data. * **Overview:** visualize trends in **Detection**, **Remediation**, and **Prevention** of security alerts. For information about accessing and using the dashboard, see [AUTOTITLE](/code-security/security-overview/viewing-security-insights). For detailed explanations of metrics and calculations, see [AUTOTITLE](/code-security/reference/security-at-scale/security-overview-dashboard-metrics). -* **Risk and Alert views:** explore the risk from security alerts of all types or focus on a single alert type and identify your risk from specific vulnerable dependencies, code weaknesses, or leaked secrets, see [AUTOTITLE](/code-security/security-overview/assessing-code-security-risk). +* **Risk:** explore the risk from security alerts of all types or focus on a single alert type and identify your risk from specific vulnerable dependencies, code weaknesses, or leaked secrets, see [AUTOTITLE](/code-security/security-overview/assessing-code-security-risk). * **Coverage:** assess the adoption of security features across repositories in the organization, see [AUTOTITLE](/code-security/security-overview/assessing-adoption-code-security).{% ifversion ghas-products %}{% ifversion secret-risk-assessment %} * **Assessments:** regardless of the enablement status of {% data variables.product.prodname_AS %} features, organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} can run a free report to scan the code in the organization for leaked secrets, see [AUTOTITLE](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/about-secret-risk-assessment).{% endif %}{% endif %}{% ifversion security-campaigns %} * **Campaigns:** coordinate and measure targeted remediation efforts, grouping related security tasks across repositories, assigning owners, and tracking progress toward defined risk‑reduction goals.{% endif %} -* **Enablement trends:** see how quickly different teams are adopting security features.{% ifversion security-overview-org-codeql-pr-alerts %} -* **CodeQL pull request alerts:** assess the impact of running CodeQL on pull requests and how development teams are resolving code scanning alerts, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).{% endif %}{% ifversion dependabot-metrics %} -**{% data variables.product.prodname_dependabot %} dashboard**: prioritize and track critical vulnerabilities by identifying, remediating, and measuring security improvements across repositories.{% endif %} -* **{% data variables.product.prodname_secret_scanning_caps %} insights:** find out which types of secret are blocked by push protection{% ifversion security-overview-delegated-bypass-requests %} and which teams are bypassing push protection{% endif %}, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection){% ifversion security-overview-delegated-bypass-requests %} and [AUTOTITLE](/code-security/security-overview/reviewing-requests-to-bypass-push-protection){% endif %}. +* **Enablement:** see how quickly different teams are adopting security features.{% ifversion security-overview-org-codeql-pr-alerts %} +* **{% data variables.product.prodname_codeql %} pull requests:** assess the impact of running {% data variables.product.prodname_codeql %} on pull requests and how development teams are resolving {% data variables.product.prodname_code_scanning %} alerts, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).{% endif %}{% ifversion dependabot-metrics %} +* **{% data variables.product.prodname_dependabot %}**: prioritize and track critical vulnerabilities by identifying, remediating, and measuring security improvements across repositories.{% endif %} +* **{% data variables.product.prodname_secret_scanning_caps %}:** find out which types of secret are blocked by push protection{% ifversion security-overview-delegated-bypass-requests %} and which teams are bypassing push protection{% endif %}, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection){% ifversion security-overview-delegated-bypass-requests %} and [AUTOTITLE](/code-security/security-overview/reviewing-requests-to-bypass-push-protection){% endif %}. {% ifversion security-campaigns %} You also create and manage security campaigns to remediate alerts from security overview, see [AUTOTITLE](/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns) and [AUTOTITLE](/code-security/securing-your-organization/fixing-security-alerts-at-scale/best-practice-fix-alerts-at-scale). diff --git a/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts.md index ecdf76919142..54ce0f72dfd4 100644 --- a/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -1,6 +1,6 @@ --- title: Viewing and updating Dependabot alerts -intro: If {% data variables.product.github %} discovers insecure dependencies in your project, you can view details on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the alert. +intro: If {% data variables.product.github %} discovers insecure dependencies in your project, you can view alert details on the {% data variables.product.prodname_dependabot %} tab of your repository. Then, you can update your project to resolve or dismiss the alert. redirect_from: - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository @@ -20,11 +20,11 @@ category: {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}. You can filter alerts by package, ecosystem, or manifest. You can sort the list of alerts, and you can click into specific alerts for more details. You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). +Your repository's {% data variables.product.prodname_dependabot %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}. You can filter alerts by package, ecosystem, or manifest. You can sort the list of alerts, and you can click into specific alerts for more details. You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). ## About updates for vulnerable dependencies in your repository -Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. +Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot %} tab filtered for that package. You can filter and sort {% data variables.product.prodname_dependabot_alerts %} using a variety of filters and sort options available on the user interface. For more information, see [Viewing and prioritizing {% data variables.product.prodname_dependabot_alerts %}](#viewing-and-prioritizing-dependabot-alerts) below. @@ -45,7 +45,7 @@ By default, alerts are sorted by **Most important**, which helps you prioritize 1. Optionally, refine the list of alerts: * Use the dropdown menus at the top of the list to sort or filter alerts. - ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab.](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png) + ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot %} tab.](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png) * Type directly in the search bar to filter alerts, including full-text search across alert details and related security advisories. * Click a label on an alert to automatically filter the list by that label. diff --git a/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/filtering-alerts-in-security-overview.md b/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/filtering-alerts-in-security-overview.md index df6f24294f60..1cfb9722d266 100644 --- a/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/filtering-alerts-in-security-overview.md +++ b/content/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/filtering-alerts-in-security-overview.md @@ -32,7 +32,7 @@ All security views have features to help you define filters. These provide an ea * **Interactive search text box.** When you click in the search box and press the keyboard "Space" key, a pop-up text box shows the filter options available in that view. You can use the mouse or keyboard arrow keys to select the options you want in the text box before pressing the keyboard "Return" key to add the filter. Supported for all views. * **Dropdown selectors and toggles.** Shown at the end of the "Search text box" or in the header of the data table. As you choose the data to view, the filters shown in the search text box are updated accordingly. Supported on the alert views. -* **Advanced filters dialog.** When you click the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** button, you can use dropdown lists to select the "Qualifier," "Operator," and "Values" for each filter. Supported on the "Overview" and metric views. +* **Advanced filters dialog.** When you click the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** button, you can use dropdown lists to select the "Qualifier," "Operator," and "Values" for each filter. Supported on the "Overview" and "Insights" views. ## Accessing security overview for your organization @@ -54,7 +54,7 @@ All security views have features to help you define filters. These provide an ea ## Using the advanced filters dialog -The advanced filters dialog is available in "Overview" and metric views and helps you build filters. +The advanced filters dialog is available in "Overview" and "Insights" views and helps you build filters. 1. In the desired view of security overview, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**. 1. In the "Advanced filters" dialog, use the dropdown lists to build your filter: diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-adoption-code-security.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-adoption-code-security.md index ed878a2abb76..e3e725972c8e 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-adoption-code-security.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-adoption-code-security.md @@ -68,7 +68,7 @@ You can view data to assess the enablement status and enablement status trends o {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. In the sidebar, under "Metrics," click **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Enablement trends**. +1. In the sidebar, under "Insights," click **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Enablement**. 1. Click on one of the tabs for "{% data variables.product.prodname_dependabot %}," "{% data variables.product.prodname_code_scanning_caps %}," or "{% data variables.product.prodname_secret_scanning_caps %}" to view enablement trends and the percentage of repositories in your organization with that feature enabled. This data is displayed as a graph and a detailed table. 1. Optionally, use the options at the top of the "Enablement trends" view page to filter the group of repositories you want to see enablement trends for. * Use the date picker to set the time range that you want to view enablement trends for. @@ -88,7 +88,7 @@ You can view data to assess the enablement status and enablement status trends o {% ifversion ghes %}{% data reusables.enterprise-accounts.access-enterprise-ghes %}{% else %}{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}{% endif %} {% data reusables.code-scanning.click-code-security-enterprise %} -1. To display the "Enablement trends" view, in the sidebar, click **Enablement trends**. +1. To display the "Enablement trends" view, in the sidebar, under "Insights", click **Enablement**. 1. Click on one of the tabs for "{% data variables.product.prodname_dependabot %}," "{% data variables.product.prodname_code_scanning_caps %}," or "{% data variables.product.prodname_secret_scanning_caps %}" to view enablement trends and the percentage of repositories across organizations in your enterprise with that feature enabled. This data is displayed as a graph and a detailed table. 1. Optionally, use the options at the top of the "Enablement trends" view page to filter the group of repositories you want to see enablement trends for. * Use the date picker to set the time range that you want to view enablement trends for. diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-code-security-risk.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-code-security-risk.md index c6ae8764098a..07be24c200df 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-code-security-risk.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-code-security-risk.md @@ -24,7 +24,7 @@ You can use the different views on your **{% data variables.product.prodname_sec * **Overview:** use to explore trends in **Detection**, **Remediation**, and **Prevention** of security alerts. * **Risk:** use to explore the current state of repositories, across all alert types.{% ifversion secret-risk-assessment %} * **Assessments:** use to explore the current state of repositories, for secret leaks specifically{% endif %} -* **Alerts views:** use to explore {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, or {% data variables.product.prodname_secret_scanning %} alerts in greater detail. +* **Findings:** use to explore {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, or {% data variables.product.prodname_secret_scanning %} alerts in greater detail. These views provide you with the data and filters to: diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality.md index 18d947714f9d..68f8b2873c0e 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality.md @@ -22,7 +22,7 @@ category: 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization. For example, from [https://github.com/settings/organizations](https://github.com/settings/organizations?ref_product=github&ref_type=engagement&ref_style=text). {% data reusables.organizations.security-overview %} -1. In the "Metrics" section of the sidebar, click {% octicon "code-square" aria-hidden="true" aria-label="code-square" %} **Code quality**. +1. In the "Insights" section of the sidebar, click {% octicon "code-square" aria-hidden="true" aria-label="code-square" %} **Code quality**. > [!NOTE] The dashboard only displays data for repositories where the viewer can see code quality findings. diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/exporting-data-from-security-overview.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/exporting-data-from-security-overview.md index 3879f69e9906..e8777f4a8436 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/exporting-data-from-security-overview.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/exporting-data-from-security-overview.md @@ -1,7 +1,7 @@ --- title: Exporting data from security overview shortTitle: Export data -intro: From security overview, you can export CSV files of the data used for your organization or enterprise's overview, risk, coverage, and {% data variables.product.prodname_codeql %} pull request alerts pages. +intro: From security overview, you can export CSV files of the data used for your organization or enterprise's overview, risk, coverage, and {% data variables.product.prodname_codeql %} pull request insights pages. permissions: '{% data reusables.permissions.security-overview %}' product: '{% data reusables.gated-features.security-overview-fpt-both %}' versions: @@ -26,7 +26,7 @@ The CSV file you download will contain data corresponding to the filters you hav {% data reusables.profile.access_org %} 1. In the "Organizations" section, select the organization for which you would like to download security overview data. {% data reusables.organizations.security-overview %} -1. In the "Security" sidebar, choose the page that you want to export data from by clicking on **{% octicon "graph" aria-hidden="true" aria-label="graph" %}Overview**, **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Coverage**, **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Risk** or **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull request alerts**. +1. In the sidebar, click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} Overview**, **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Coverage**, **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Risk**, or **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull requests**. 1. Next to the search bar, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Export CSV**. It may take a moment for {% data variables.product.github %} to generate the CSV file of your data. Once the CSV file generates, the file will automatically start downloading, and a banner will appear confirming your report is ready. If you are downloading the CSV from the overview page, you will also receive an email when your report is ready, containing a link to download the CSV. diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-dependabot-alerts.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-dependabot-alerts.md index 9d431ea1b149..1887963c9e44 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-dependabot-alerts.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-dependabot-alerts.md @@ -22,7 +22,7 @@ This article explains how to access and view these metrics for your organization {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. In the sidebar, under "Metrics", click **{% octicon "dependabot" aria-hidden="true" aria-label="dependabot" %} {% data variables.product.prodname_dependabot %} dashboard**. +1. In the sidebar, under "Insights", click **{% octicon "dependabot" aria-hidden="true" aria-label="dependabot" %} {% data variables.product.prodname_dependabot %} dashboard**. 1. Optionally, use the filters at your disposal, or build your own filters. {% data reusables.security-overview.dependabot-filters-link %} 1. Optionally, click on a number on the x-axis of the chart to filter the alert list by the relevant criteria (for example `has:patch severity:critical,high epss_percentage:>=0.01`). 1. Optionally, click on an individual repository to see the associated {% data variables.product.prodname_dependabot_alerts %}. @@ -33,7 +33,7 @@ The default funnel order is `has:patch, severity:critical,high, epss_percentage> {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. In the sidebar, under "Metrics", click **{% octicon "dependabot" aria-hidden="true" aria-label="dependabot" %} {% data variables.product.prodname_dependabot %} dashboard**. +1. In the sidebar, under "Insights", click **{% octicon "dependabot" aria-hidden="true" aria-label="dependabot" %} {% data variables.product.prodname_dependabot %} dashboard**. 1. On the top right of the "Alert prioritization" graph, click {% octicon "gear" aria-label="Configure funnel categories" %}. 1. In the "Configure funnel order" dialog, move the criteria as desired. 1. Once you're done, click **Move** to save your changes. diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts.md index 658d13891b4f..65fb04ffb9e8 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts.md @@ -14,11 +14,11 @@ category: - Secure at scale --- -## Viewing {% data variables.product.prodname_codeql %} pull request alerts metrics for an organization +## Viewing {% data variables.product.prodname_codeql %} pull request metrics for an organization {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull request alerts**. +1. In the sidebar, under "Insights", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull requests**. 1. Optionally, use the date picker to set the time range. The date picker will show data based on the pull request alerts' creation dates. 1. Optionally, apply filters in the search box at the top of the page. 1. Alternatively, you can open the advanced filter dialog: @@ -28,12 +28,12 @@ category: * Optionally, to remove a filter from your search, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**. In the row of the filter you want to remove, click {% octicon "x" aria-label="Delete FILTER-NUMBER: FILTER-PROPERTIES" %}, then click **Apply**.{% ifversion security-overview-export-data %} 1. You can use the **{% octicon "download" aria-hidden="true" aria-label="download" %} Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %} -## Viewing {% data variables.product.prodname_codeql %} pull request alerts metrics for your enterprise +## Viewing {% data variables.product.prodname_codeql %} pull request metrics for your enterprise -You can also view metrics for {% data variables.product.prodname_codeql %} alerts in pull requests across organizations in your enterprise. +You can also view metrics for {% data variables.product.prodname_codeql %} pull request alerts across organizations in your enterprise. {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.code-scanning.click-code-security-enterprise %} -1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull request alerts**. +1. In the sidebar, under "Insights", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull requests**. {% data reusables.security-overview.enterprise-filters-tip %} diff --git a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection.md b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection.md index 9ab5f6122cf2..926e3948ee0a 100644 --- a/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection.md +++ b/content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection.md @@ -1,6 +1,6 @@ --- -title: Viewing metrics for secret scanning push protection -shortTitle: View secret scanning metrics +title: Viewing metrics for {% data variables.product.prodname_secret_scanning %} push protection +shortTitle: View {% data variables.product.prodname_secret_scanning %} metrics allowTitleToDifferFromFilename: true intro: Monitor push protection's performance across your organization{% ifversion security-overview-enterprise-secret-scanning-metrics %} or enterprise{% endif %} to identify repositories where you may need to take action. permissions: '{% data reusables.permissions.security-overview %}' @@ -23,7 +23,7 @@ category: {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_secret_scanning_caps %}**. +1. In the sidebar, under "Insights", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_secret_scanning_caps %}**. 1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your organization. {% data reusables.security-overview.filter-secret-scanning-metrics %} @@ -33,7 +33,7 @@ You can view metrics for {% data variables.product.prodname_secret_scanning %} p {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.code-scanning.click-code-security-enterprise %} -1. In the sidebar, click **{% data variables.product.prodname_secret_scanning_caps %} metrics**. +1. In the sidebar, click **{% data variables.product.prodname_secret_scanning_caps %}**. 1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your enterprise. {% data reusables.security-overview.filter-secret-scanning-metrics %} diff --git a/content/code-security/reference/security-at-scale/available-filters-for-security-overview.md b/content/code-security/reference/security-at-scale/available-filters-for-security-overview.md index f166e68768ff..f2474f59e44b 100644 --- a/content/code-security/reference/security-at-scale/available-filters-for-security-overview.md +++ b/content/code-security/reference/security-at-scale/available-filters-for-security-overview.md @@ -167,7 +167,7 @@ You can limit the data to repositories owned by a single organization in your en ## Production context filters -**Available in:** {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alert views +**Available in:** {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} views {% data reusables.security.production-context-mdc-preview %} @@ -181,10 +181,10 @@ For more information about production context, see [AUTOTITLE](/code-security/se {% endif %} -## {% data variables.product.prodname_dependabot %} alert view filters +## {% data variables.product.prodname_dependabot %} view filters **Available in:** -* {% data variables.product.prodname_dependabot_alerts %} view{% ifversion dependabot-malware-alerts %} +* {% data variables.product.prodname_dependabot %} view{% ifversion dependabot-malware-alerts %} * {% data variables.product.prodname_dependabot_malware_alerts %} view{% endif %} | Qualifier | Description | @@ -223,9 +223,9 @@ Alternatively, you can use complex filters by clicking **{% octicon "filter" ari {% endif %} -## {% data variables.product.prodname_code_scanning_caps %} alert view filters +## {% data variables.product.prodname_code_scanning_caps %} view filters -**Available in:** {% data variables.product.prodname_code_scanning %} alert view +**Available in:** {% data variables.product.prodname_code_scanning %} view You can click any result to see full details of the relevant query and the line of code that triggered the alert. @@ -238,9 +238,9 @@ You can click any result to see full details of the relevant query and the line |`sort`|Display alerts from newest to oldest (`created-desc`), oldest to newest (`created-asc`), most recently updated (`updated-desc`), or least recently updated (`updated-asc`).| |`tool`|Display {% data variables.product.prodname_code_scanning %} alerts detected by the specified tool, for example: `tool:CodeQL` for alerts created using the {% data variables.product.prodname_codeql %} application in {% data variables.product.prodname_dotcom %}.| -## {% data variables.product.prodname_secret_scanning_caps %} alert view filters +## {% data variables.product.prodname_secret_scanning_caps %} view filters -**Available in:** {% data variables.product.prodname_secret_scanning %} alert view +**Available in:** {% data variables.product.prodname_secret_scanning %} view | Qualifier | Description | | -------- | -------- | diff --git a/content/code-security/reference/supply-chain-security/automatic-dependency-submission.md b/content/code-security/reference/supply-chain-security/automatic-dependency-submission.md index f67c73da52dd..eead392fa978 100644 --- a/content/code-security/reference/supply-chain-security/automatic-dependency-submission.md +++ b/content/code-security/reference/supply-chain-security/automatic-dependency-submission.md @@ -82,7 +82,7 @@ Automatic dependency submission makes a best effort to cache package downloads b For Maven projects, automatic dependency submission runs an open source fork of the [Maven Dependency Tree Dependency Submission](https://github.com/marketplace/actions/maven-dependency-tree-dependency-submission). The fork allows {% data variables.product.github %} to stay in sync with the upstream repository plus maintain some changes that are only applicable to automatic submission. The fork's source is available at [advanced-security/maven-dependency-submission-action](https://github.com/advanced-security/maven-dependency-submission-action). -If your repository's dependencies seem inaccurate, check that the timestamp of the last dependency graph build matches the last change to your `pom.xml` file. The timestamp is visible on the table of alerts in the repository's {% data variables.product.prodname_dependabot_alerts %} tab. Pushing a commit which updates `pom.xml` will trigger a new run of the Dependency Tree Submission action and force a rebuild of that repository's dependency graph. +If your repository's dependencies seem inaccurate, check that the timestamp of the last dependency graph build matches the last change to your `pom.xml` file. The timestamp is visible on the table of alerts in the repository's {% data variables.product.prodname_dependabot %} tab. Pushing a commit which updates `pom.xml` will trigger a new run of the Dependency Tree Submission action and force a rebuild of that repository's dependency graph. ### Gradle projects diff --git a/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/troubleshooting-the-dependency-graph.md b/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/troubleshooting-the-dependency-graph.md index ff53b99fc621..52bb7528aff3 100644 --- a/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/troubleshooting-the-dependency-graph.md +++ b/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/troubleshooting-the-dependency-graph.md @@ -62,7 +62,7 @@ Manifest files stored in directories with names that are typically used for vend If the table of dependencies for your project doesn't accurately represent your repository's manifests, you can trigger a rebuild of its dependency graph. -From the repository's {% data variables.product.prodname_dependabot_alerts %} tab, click {% octicon "gear" aria-label="settings" %} at the top of the alert list. Select **Refresh {% data variables.product.prodname_dependabot_alerts %}** from the dropdown menu. This will enqueue a background task to process the repository's manifests, detect any new or changed dependencies, and update the alerts. +From the repository's {% data variables.product.prodname_dependabot %} tab, click {% octicon "gear" aria-label="settings" %} at the top of the alert list. Select **Refresh {% data variables.product.prodname_dependabot_alerts %}** from the dropdown menu. This will enqueue a background task to process the repository's manifests, detect any new or changed dependencies, and update the alerts. >[!NOTE] You need to have permission to manage security alerts in order to refresh a repository's dependency graph. See [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for information on configuring this access. To further reduce the potential for abuse, the **Refresh {% data variables.product.prodname_dependabot_alerts %}** option can only be triggered once an hour per repository. diff --git a/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/vulnerable-dependency-detection.md b/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/vulnerable-dependency-detection.md index afe32224e02f..b3d3be07dc20 100644 --- a/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/vulnerable-dependency-detection.md +++ b/content/code-security/reference/supply-chain-security/troubleshoot-dependabot/vulnerable-dependency-detection.md @@ -67,11 +67,11 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) +![Screenshot of the {% data variables.product.prodname_dependabot %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot %} tab filtered to display vulnerabilities for that dependent package and manifest. -![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) +![Screenshot of the {% data variables.product.prodname_dependabot %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. diff --git a/content/code-security/tutorials/secure-your-dependencies/dependabot-quickstart-guide.md b/content/code-security/tutorials/secure-your-dependencies/dependabot-quickstart-guide.md index c0868814fe6e..a4c5f34e62c3 100644 --- a/content/code-security/tutorials/secure-your-dependencies/dependabot-quickstart-guide.md +++ b/content/code-security/tutorials/secure-your-dependencies/dependabot-quickstart-guide.md @@ -92,7 +92,7 @@ For more information about viewing, prioritizing, and sorting {% data variables. You can fix or dismiss {% data variables.product.prodname_dependabot_alerts %} on {% data variables.product.prodname_dotcom %}. Let's continue to use the forked repository as an example, and the "Command Injection in lodash" alert described in the previous section. -1. Navigate to the {% data variables.product.prodname_dependabot_alerts %} tab for the repository. For more information, see the [Viewing {% data variables.product.prodname_dependabot_alerts %} for your repository](#viewing-dependabot-alerts-for-your-repository) section above. +1. Navigate to the {% data variables.product.prodname_dependabot %} tab for the repository. For more information, see the [Viewing {% data variables.product.prodname_dependabot_alerts %} for your repository](#viewing-dependabot-alerts-for-your-repository) section above. 1. Click an alert. 1. Click the "Command Injection in lodash" alert on the `javascript/package-lock.json` file. 1. Review the alert. You can: diff --git a/content/code-security/tutorials/secure-your-organization/organizing-remediation-efforts-for-leaked-secrets.md b/content/code-security/tutorials/secure-your-organization/organizing-remediation-efforts-for-leaked-secrets.md index 1c53765bac07..50a70028fa31 100644 --- a/content/code-security/tutorials/secure-your-organization/organizing-remediation-efforts-for-leaked-secrets.md +++ b/content/code-security/tutorials/secure-your-organization/organizing-remediation-efforts-for-leaked-secrets.md @@ -33,7 +33,7 @@ Before taking action, you need to understand the current state of your organizat {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. In the left sidebar, under "Alerts", click the {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} symbol to the right of **{% data variables.product.prodname_secret_scanning_caps %}**. +1. In the left sidebar, under "Findings", click the {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} symbol to the right of **{% data variables.product.prodname_secret_scanning_caps %}**. 1. In the dropdown list, select `Default`. `Default` relates to supported patterns and specified custom patterns. 1. Alternatively, you can select `Generic` to review unstructured secrets like passwords. However, generic patterns typically produce more false positives than default patterns, so consider reviewing these alerts after addressing higher-priority leaks. 1. Review the total number of open alerts and repositories affected. @@ -44,7 +44,7 @@ Before taking action, you need to understand the current state of your organizat * To filter by specific **service** credentials (AWS, Azure, {% data variables.product.github %}), use `provider:`. * To filter by specific **token types**, use `secret-type:`. -1. Optionally, in the sidebar under "Metrics," click **{% data variables.product.prodname_secret_scanning_caps %}** to see: +1. Optionally, in the sidebar under "Insights," click **{% data variables.product.prodname_secret_scanning_caps %}** to see: * Secret types that have been blocked or bypassed most frequently * Repositories with the most blocked pushes or bypasses diff --git a/content/code-security/tutorials/secure-your-organization/prioritize-alerts-in-production-code.md b/content/code-security/tutorials/secure-your-organization/prioritize-alerts-in-production-code.md index 94652248a570..2f4d9debf886 100644 --- a/content/code-security/tutorials/secure-your-organization/prioritize-alerts-in-production-code.md +++ b/content/code-security/tutorials/secure-your-organization/prioritize-alerts-in-production-code.md @@ -31,10 +31,10 @@ For more information on updating records, see [AUTOTITLE](/code-security/how-tos ## 2. Use production context filters -Production context filters are made available in alert views and security campaign views under the **{% data variables.product.prodname_security_and_quality_tab %}** tab. +Production context filters are made available in the **{% data variables.product.prodname_security_and_quality_tab %}** tab. -* **{% data variables.product.prodname_dependabot_alerts %} view**: See [Viewing {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts). -* **{% data variables.product.prodname_code_scanning_caps %} alerts view**: See [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository). +* **{% data variables.product.prodname_dependabot %} view**: See [AUTOTITLE](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts). +* **{% data variables.product.prodname_code_scanning_caps %} view**: See [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository). * **Security campaign view**: See [AUTOTITLE](/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns). Once the alert list is displayed, use the `artifact-registry-url` or `artifact-registry` filters in organization views to focus on vulnerabilities affecting artifacts present in production. diff --git a/content/copilot/concepts/agents/copilot-cli/about-remote-access.md b/content/copilot/concepts/agents/copilot-cli/about-remote-access.md new file mode 100644 index 000000000000..e61bd5be441e --- /dev/null +++ b/content/copilot/concepts/agents/copilot-cli/about-remote-access.md @@ -0,0 +1,91 @@ +--- +title: About remote access to {% data variables.copilot.copilot_cli %} sessions +shortTitle: About remote access +intro: 'Access a running {% data variables.copilot.copilot_cli_short %} session from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_mobile %} to monitor and steer the session when you are away from the machine where the session is running.' +versions: + feature: copilot +contentType: concepts +category: + - Learn about Copilot # Copilot discovery page + - Learn about Copilot CLI # Copilot CLI bespoke page +docsTeamMetrics: + - copilot-cli +--- + +This article explains the concepts around remote access to {% data variables.copilot.copilot_cli_short %} sessions. For instructions on how to enable remote access, see [AUTOTITLE](/copilot/how-tos/copilot-cli/steer-remotely). + +## Introduction + +When you start a {% data variables.copilot.copilot_cli %} session on your local machine, the session is normally only accessible from the terminal where you started it. However, you can enable remote access to the session from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_mobile %}, allowing you to view the progress of a task that {% data variables.product.prodname_copilot_short %} is working on, and respond to prompts for more information, or requests for permissions. + +This is useful in scenarios such as: + +* **Leaving your workstation**: You started a session on your laptop and were then called away, or you finished work for the day, but you want to continue interacting with {% data variables.product.prodname_copilot_short %} without having to return to the machine. + +* **Monitoring a long-running task**: You started a complex task that will take time to complete, but didn't give {% data variables.product.prodname_copilot_short %} full permission to carry out every action. You need to periodically assess and respond to permission requests to allow a task to continue. + + To ensure the stability of the remote access feature there is a 60 MB limit on size of session output that is passed to the remote interface. As a result, very long-running sessions that generate large amounts of output may experience reduced performance in the remote interface. The local terminal session is unaffected. + +* **Quick access from a mobile device**: You're working on something else now but you're using {% data variables.product.prodname_mobile %} to provide an at-a-glance view of progress on a task you started in {% data variables.copilot.copilot_cli_short %}. + +{% data reusables.cli.public-preview-remote-access %} + +## Prerequisites + +Remote access requires: + +* **Policy enablement**: For users who have a {% data variables.product.prodname_copilot_short %} seat from an organization, remote access access is governed by policies set at the organization and enterprise level. The "Remote Control" policy is off by default but can be enabled by an enterprise or organization owner. See [Administering remote access](#administering-remote-access). +* **A {% data variables.product.github %} repository**: The working directory where you started the CLI must contain a Git repository hosted on {% data variables.product.prodname_dotcom_the_website %}. If you attempt to enable remote access outside of a {% data variables.product.prodname_dotcom %} repository, the CLI displays the message: "Remote session disabled: not in a {% data variables.product.github %} repository" +* **The machine must be online**: The CLI session must be actively running in a terminal on a machine with an internet connection. If the machine goes to sleep or loses its connection, remote access is unavailable until the machine is back online. See [Reconnection](#reconnection) later in this article. +* **An interactive session**: Remote access is only available for interactive sessions. It is not available when you use the CLI programmatically with the `--prompt` command-line option, for example when you use the CLI in a script. + +## Accessing a session remotely + +When you enable remote access for a {% data variables.copilot.copilot_cli_short %} session, you can go to {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_mobile %} and find the session in the list of your recent agent sessions. The remote interface is updated in real time, allowing you to monitor ongoing output from the session and respond to prompts and permission requests as they come in. + +Both the local terminal and the remote interface are active at the same time. You can enter commands in either interface. {% data variables.copilot.copilot_cli_short %} uses the first response it receives to any prompt or permission request. + +Your session continues to run on your local machine. The remote interface provides a way to interact with the session, but the CLI itself—and all the tools, shell commands, and file operations it runs—remain on the machine where you started the session. + +## What you can do remotely + +When connected to a session remotely from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_mobile %}, you can: + +* **Respond to permission requests**: Approve or deny tool, file path, and URL permission requests. +* **Respond to questions**: Answer when {% data variables.product.prodname_copilot_short %} asks you to supply more information or make a decision. +* **Approve or reject plans**: Respond to plan approval prompts when {% data variables.product.prodname_copilot_short %} is in plan mode. +* **Submit new prompts**: Enter questions or instructions, just as you would in the terminal. +* **Switch modes**: Change the session mode—for example, between interactive and plan mode. +* **End the current operation**: Cancel the agent's current work. + +{% data reusables.cli.remote-access-slash-commands %} + +## Reconnection + +If the connection between your local machine and {% data variables.product.prodname_dotcom %} is temporarily lost—for example, due to a network interruption—you can continue using the session remotely as soon as the connection is restored. + +You can use the `/keep-alive` slash command to prevent your machine from going to sleep. See [Preventing your machine from going to sleep](/copilot/how-tos/copilot-cli/steer-remotely#preventing-your-machine-from-going-to-sleep). + +If you closed a session that had remote access enabled, when you resume the session—either using `copilot --continue` or `copilot --resume=ID`—you must re-enable remote access. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/steer-remotely#resuming-a-session-with-remote-access). + +## Visibility of remote access sessions + +Remote access is only available to you—the person who is signed in to {% data variables.product.prodname_dotcom %} with the same account that started the CLI session. No one else can view or interact with your session remotely. + +### Points to note + +When you enable remote access: + +* Session events are sent from your local machine to {% data variables.product.prodname_dotcom %}. This includes conversation messages, tool execution events, and permission requests. +* Remote commands are polled by {% data variables.copilot.copilot_cli_short %} from {% data variables.product.prodname_dotcom %} and injected into your local session. +* The CLI itself continues to run locally. All shell commands, file operations, and tool executions happen on your machine—remote access does not grant any direct access to your local machine beyond what the CLI agent can do within the session. + +The remote session link (displayed in the CLI when you enable remote access) points to a session-specific URL on {% data variables.product.prodname_dotcom_the_website %}. Only authenticated users with the correct account can access this URL. + +## Administering remote access + +The ability for users enable remote access to their {% data variables.copilot.copilot_cli_short %} sessions can be controlled by policies in the enterprise or organization settings. Users who get {% data variables.product.prodname_copilot_short %} from an organization will not be able to use remote access if it has been disabled at the organization or enterprise level. + +The "Remote Control" policy is off by default, so it must be enabled by an enterprise or organization owner before users can start monitoring and steering their CLI sessions remotely. + +For more information about setting policies for your enterprise or organization, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies) and [AUTOTITLE](/copilot/how-tos/copilot-cli/administer-copilot-cli-for-your-enterprise). diff --git a/content/copilot/concepts/agents/copilot-cli/fleet.md b/content/copilot/concepts/agents/copilot-cli/fleet.md index f91ba448f606..d3993fcad913 100644 --- a/content/copilot/concepts/agents/copilot-cli/fleet.md +++ b/content/copilot/concepts/agents/copilot-cli/fleet.md @@ -17,7 +17,7 @@ docsTeamMetrics: The `/fleet` slash command in {% data variables.copilot.copilot_cli_short %} is designed to take an implementation plan and break it down into smaller, independent tasks that can be executed in parallel by subagents. This allows for faster completion of complex requests that involve multiple steps. -This article gives an overview of the `/fleet` slash command. For details of how to use it, see [AUTOTITLE](/copilot/how-tos/copilot-cli/speeding-up-task-completion). +This article gives an overview of the `/fleet` slash command. For details of how to use it, see [AUTOTITLE](/copilot/how-tos/copilot-cli/speed-up-task-completion). ## How `/fleet` works @@ -70,6 +70,6 @@ For more information about autopilot mode, see [AUTOTITLE](/copilot/concepts/age ## Further reading -* [AUTOTITLE](/copilot/how-tos/copilot-cli/speeding-up-task-completion) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/speed-up-task-completion) * [AUTOTITLE](/copilot/how-tos/copilot-cli) * [AUTOTITLE](/copilot/how-tos/use-copilot-agents/use-copilot-cli) diff --git a/content/copilot/concepts/agents/copilot-cli/index.md b/content/copilot/concepts/agents/copilot-cli/index.md index 9a6b524ff8cd..bd99c879e093 100644 --- a/content/copilot/concepts/agents/copilot-cli/index.md +++ b/content/copilot/concepts/agents/copilot-cli/index.md @@ -7,9 +7,10 @@ versions: feature: copilot children: - /about-copilot-cli + - /comparing-cli-features + - /about-remote-access - /about-custom-agents - /about-cli-plugins - - /comparing-cli-features - /autopilot - /fleet - /research diff --git a/content/copilot/how-tos/copilot-cli/index.md b/content/copilot/how-tos/copilot-cli/index.md index 9f966eaca891..28e60dab6bac 100644 --- a/content/copilot/how-tos/copilot-cli/index.md +++ b/content/copilot/how-tos/copilot-cli/index.md @@ -18,18 +18,20 @@ children: - /cli-best-practices - /set-up-copilot-cli - /allowing-tools + - /steer-remotely - /automate-copilot-cli - /customize-copilot - /connecting-vs-code - /use-copilot-cli-agents - /administer-copilot-cli-for-your-enterprise - - /speeding-up-task-completion + - /speed-up-task-completion - /chronicle - /content/copilot/concepts/agents/copilot-cli/about-copilot-cli - /content/copilot/concepts/agents/copilot-cli/comparing-cli-features - /content/copilot/concepts/agents/about-agent-skills - /content/copilot/concepts/agents/copilot-cli/about-cli-plugins - /content/copilot/concepts/agents/copilot-cli/autopilot + - /content/copilot/concepts/agents/copilot-cli/about-remote-access - /content/copilot/concepts/agents/copilot-cli/fleet - /content/copilot/concepts/agents/copilot-cli/research - /content/copilot/concepts/agents/copilot-cli/chronicle diff --git a/content/copilot/how-tos/copilot-cli/speeding-up-task-completion.md b/content/copilot/how-tos/copilot-cli/speed-up-task-completion.md similarity index 95% rename from content/copilot/how-tos/copilot-cli/speeding-up-task-completion.md rename to content/copilot/how-tos/copilot-cli/speed-up-task-completion.md index 3364d7014b96..65f3bb526629 100644 --- a/content/copilot/how-tos/copilot-cli/speeding-up-task-completion.md +++ b/content/copilot/how-tos/copilot-cli/speed-up-task-completion.md @@ -1,10 +1,12 @@ --- title: Speeding up task completion with the `/fleet` command -shortTitle: Speeding up task completion +shortTitle: Speed up task completion intro: Learn how you can speed up the completion of a multi-step implementation plan by using the `/fleet` slash command. versions: feature: copilot contentType: how-tos +redirect_from: + - /copilot/how-tos/copilot-cli/speeding-up-task-completion category: - Author and optimize with Copilot # Copilot discovery page - Build with Copilot CLI # Copilot CLI bespoke page diff --git a/content/copilot/how-tos/copilot-cli/steer-remotely.md b/content/copilot/how-tos/copilot-cli/steer-remotely.md new file mode 100644 index 000000000000..ced6f695a5da --- /dev/null +++ b/content/copilot/how-tos/copilot-cli/steer-remotely.md @@ -0,0 +1,149 @@ +--- +title: Steering a {% data variables.copilot.copilot_cli %} session from another device +shortTitle: Steer a session remotely +allowTitleToDifferFromFilename: true +intro: 'Enable remote access to a {% data variables.copilot.copilot_cli_short %} session so you can monitor progress, respond to prompts, and continue working from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_mobile %}.' +versions: + feature: copilot +contentType: how-tos +category: + - Author and optimize with Copilot # Copilot discovery page + - Build with Copilot CLI # Copilot CLI bespoke page +docsTeamMetrics: + - copilot-cli +--- + +Remote access lets you connect to a running {% data variables.copilot.copilot_cli_short %} session from any browser or from {% data variables.product.prodname_mobile %}. You can view session output, respond to permission requests, and continue working in the session without being at the machine where the session is running. + +This article explains how to enable and use remote access. For more conceptual information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-remote-access). + +{% data reusables.cli.public-preview-remote-access %} + +## Prerequisites + +* The machine where the CLI session is running must be online, with the session actively running in a terminal. + + > [!TIP] + > Use the `/keep-alive` slash command to prevent your machine from going to sleep while you're away. See [Preventing your machine from going to sleep](#preventing-your-machine-from-going-to-sleep). + +* The working directory must contain a Git repository hosted on {% data variables.product.prodname_dotcom_the_website %}. If you are not in a {% data variables.product.prodname_dotcom %} repository, the CLI displays: "Remote session disabled: not in a {% data variables.product.github %} repository." + +## Enabling remote access for a session + +You can enable remote access in three ways: + +* With a slash command during an interactive session. +* With a command-line option when you start {% data variables.copilot.copilot_cli_short %}. +* By configuring the CLI to enable remote access by default for all interactive sessions. + +### Using the `/remote` slash command + +If you are already in an interactive session and want to enable remote access, enter: + +```copilot copy +/remote +``` + +The CLI connects to {% data variables.product.prodname_dotcom_the_website %} and displays details for accessing the session remotely—see [Accessing a session from {% data variables.product.prodname_dotcom_the_website %}](#accessing-a-session-from-githubcom) and [Accessing a session from {% data variables.product.prodname_mobile %}](#accessing-a-session-from-github-mobile) later in this article. + +### Using the `--remote` command-line option + +If you think you may want to access a session remotely, you can start the CLI with the `--remote` command-line option. This avoids the need to remember to use the `/remote` slash command during the session. + +```bash copy +copilot --remote +``` + +Details for accessing the session remotely are displayed when the interactive session starts and can be displayed again at any time by using the `/remote` slash command. + +### Configuring remote access to always be enabled + +If you always want your interactive CLI sessions to be remotely accessible, add the following to your {% data variables.product.prodname_copilot_short %} configuration file (typically located at `~/.copilot/config.json`): + +```json copy +{ + "remoteSessions": true +} +``` + +To override this setting for a particular session, use the `--no-remote` option when you start the session: + +```bash copy +copilot --no-remote +``` + +> [!NOTE] +> The command-line options `--remote` and `--no-remote` always take precedence over the `remoteSessions` setting in the configuration file. + +## Accessing a session from {% data variables.product.prodname_dotcom_the_website %} + +When remote access is enabled, the CLI displays a link in the format: + +```text +https://github.com/OWNER/REPO/tasks/TASK_ID +``` + +Use this link to access the session in a web browser. You must be signed in to {% data variables.product.prodname_dotcom %} with the same account that started the CLI session. + +You can also access the session from your list of recent agent sessions on {% data variables.product.prodname_dotcom_the_website %}: + +1. In the top-left corner of {% data variables.product.prodname_dotcom %}, click {% octicon "three-bars" aria-label="Open menu" %}. +1. Click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**. +1. Under "Recent agent sessions", click your {% data variables.copilot.copilot_cli_short %} session to open it. + +> [!IMPORTANT] +> Sessions are user-specific: you can only access your own {% data variables.copilot.copilot_cli_short %} sessions. Other {% data variables.product.github %} users cannot access your sessions. + +## Accessing a session from {% data variables.product.prodname_mobile %} + +A {% data variables.copilot.copilot_cli_short %} session is available in {% data variables.product.prodname_mobile %} as soon as you enable remote access. To find your session in {% data variables.product.prodname_mobile %}: + +1. Tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** button in the bottom right corner of the screen. + + The session is listed under "Agent sessions." + +1. Tap the session to open it. + +### Use a QR code to quickly open a session on your phone + +1. In an interactive session, enter the `/remote` slash command to redisplay the remote session details. +1. Press Ctrl+E to toggle on/off display of a QR code. + + > [!NOTE] + > This keyboard shortcut expands/collapses all details in the session conversation, not just the QR code. It only works if the input field is currently empty. + +1. Scan the QR code with your phone to go directly to the session in {% data variables.product.prodname_mobile %}. + +## Preventing your machine from going to sleep + +You can use the `/keep-alive` slash command to prevent your machine from going to sleep. This allows you to maintain the remote connection and continue interacting with the session from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_mobile %}. + +In an interactive session, enter `/keep-alive OPTION`, where `OPTION` is one of: + +* `on`: Prevents the machine from going to sleep while the CLI session is active. +* `off`: Allows the machine to go to sleep as normal. +* `busy`: Prevents the machine from going to sleep only while {% data variables.product.prodname_copilot_short %} is working on a task. Once the agent completes a task the machine can go to sleep as normal. The machine will not go to sleep if {% data variables.product.prodname_copilot_short %} is waiting for you to respond to a request for input from you. +* `NUMBERm`, `NUMBERh`, or `NUMBERd` (for example, `30m`, `8h`, `1d`): Prevents the machine from going to sleep for a specific number of minutes, hours, or days. If a bare number is provided without a suffix, it is treated as minutes. + +Without passing an `OPTION`, the `/keep-alive` command displays the current keep-alive status. + +## Resuming a session with remote access + +When you shut down a session that has remote access enabled, the CLI displays a resume command that includes `--remote`: + +```bash +copilot --resume=SESSION_ID --remote +``` + +Use this command to restart the session with remote access enabled. + +Similarly, adding `--remote` to a `copilot --continue` command resumes the most recent session with remote access enabled. + +If you have `"remoteSessions": true` in your {% data variables.product.prodname_copilot_short %} configuration file, resumed sessions will have remote access enabled automatically and you do not need to use the `--remote` option. + +## Preventing remote access + +Remote access is disabled by default, but may be enabled in your {% data variables.product.prodname_copilot_short %} configuration file. You can ensure a session is not remotely accessible by: + +* **For a single session**: Start the CLI with `--no-remote` to prevent remote access for that session, regardless of your configuration file setting. +* **Permanently**: Remove the `"remoteSessions": true` setting from your {% data variables.product.prodname_copilot_short %} configuration file (or set it to `false`). diff --git a/content/copilot/reference/copilot-cli-reference/cli-command-reference.md b/content/copilot/reference/copilot-cli-reference/cli-command-reference.md index de8bd659f647..de7fe6931c46 100644 --- a/content/copilot/reference/copilot-cli-reference/cli-command-reference.md +++ b/content/copilot/reference/copilot-cli-reference/cli-command-reference.md @@ -26,6 +26,7 @@ docsTeamMetrics: | `copilot login` | Authenticate with {% data variables.product.prodname_copilot_short %} via the OAuth device flow. Accepts `--host HOST` to specify the {% data variables.product.github %} host URL (default: `https://github.com`). | | `copilot logout` | Sign out of {% data variables.product.github %} and remove stored credentials. | | `copilot plugin` | Manage plugins and plugin marketplaces. | +| `copilot mcp` | Manage MCP server configurations from the command line. | ## Global shortcuts in the interactive interface @@ -42,11 +43,11 @@ docsTeamMetrics: ## Timeline shortcuts in the interactive interface -| Shortcut | Purpose | -|-------------------------------------|---------------------------------------| -| ctrl+o | While there is nothing in the prompt input, this expands recent items in {% data variables.product.prodname_copilot_short %}'s response timeline to show more details. | -| ctrl+e | While there is nothing in the prompt input, this expands all items in {% data variables.product.prodname_copilot_short %}'s response timeline. | -| ctrl+t | Expand/collapse display of reasoning in responses. | +| Shortcut | Purpose | +|------------------------------|---------------------------------------| +| Ctrl+O | While there is nothing in the prompt input, this expands recent items in {% data variables.product.prodname_copilot_short %}'s response timeline to show more details. | +| Ctrl+E | While there is nothing in the prompt input, this expands all items in {% data variables.product.prodname_copilot_short %}'s response timeline. | +| Ctrl+T | Expand/collapse display of reasoning in responses. | ## Navigation shortcuts in the interactive interface @@ -92,6 +93,7 @@ docsTeamMetrics: | `/ide` | Connect to an IDE workspace. | | `/init` | Initialize {% data variables.product.prodname_copilot_short %} custom instructions and agentic features for this repository. | | `/instructions` | View and toggle custom instruction files. | +| `/keep-alive [on\|busy\|NUMBERm\|NUMBERh]` | Prevent the machine from going to sleep: while a CLI session is active, while the agent is busy, or for a defined length of time. | | `/list-dirs` | Display all of the directories for which file access has been allowed. | | `/login` | Log in to {% data variables.product.prodname_copilot_short %}. | | `/logout` | Log out of {% data variables.product.prodname_copilot_short %}. | @@ -102,6 +104,7 @@ docsTeamMetrics: | `/plan [PROMPT]` | Create an implementation plan before coding. | | `/plugin [marketplace\|install\|uninstall\|update\|list] [ARGS...]` | Manage plugins and plugin marketplaces. | | `/pr [view\|create\|fix\|auto]` | Operate on pull requests for the current branch. | +| `/remote` | Enable remote access to this session from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_mobile %}. | | `/rename [NAME]` | Rename the current session (auto-generates a name if omitted; alias for `/session rename`). | | `/reset-allowed-tools` | Reset the list of allowed tools. | | `/restart` | Restart the CLI, preserving the current session. | @@ -165,10 +168,12 @@ For a complete list of available slash commands enter `/help` in the CLI's inter | `--no-custom-instructions` | Disable loading of custom instructions from `AGENTS.md` and related files. | | `--no-experimental` | Disable experimental features. | | `--no-mouse` | Disable mouse support. | +| `--no-remote` | Disable remote access for this session. | | `--output-format=FORMAT` | FORMAT can be `text` (default) or `json` (outputs JSONL: one JSON object per line). | | `-p PROMPT`, `--prompt=PROMPT` | Execute a prompt programmatically (exits after completion). | | `--plain-diff` | Disable rich diff rendering (syntax highlighting via the diff tool specified by your git config). | | `--plugin-dir=DIRECTORY` | Load a plugin from a local directory (can be used multiple times). | +| `--remote` | Enable remote access to this session from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_mobile %}. | | `--resume=SESSION-ID` | Resume a previous interactive session by choosing from a list (optionally specify a session ID). | | `-s`, `--silent` | Output only the agent response (without usage statistics), useful for scripting with `-p`. | | `--screen-reader` | Enable screen reader optimizations. | @@ -272,6 +277,8 @@ copilot --allow-tool='MyMCP' | `COPILOT_GITHUB_TOKEN` | Authentication token. Takes precedence over `GH_TOKEN` and `GITHUB_TOKEN`. | | `COPILOT_HOME` | Override the configuration and state directory. Default: `$HOME/.copilot`. | | `COPILOT_CACHE_HOME` | Override the cache directory (used for marketplace caches, auto-update packages, and other ephemeral data). See [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-config-dir-reference#changing-the-location-of-the-configuration-directory) for platform defaults. | +| `COPILOT_SUBAGENT_MAX_DEPTH` | Maximum subagent nesting depth. Default: `6`. Range: `1`–`256`. | +| `COPILOT_SUBAGENT_MAX_CONCURRENT` | Maximum concurrent subagents across the entire session tree. Default: `32`. Range: `1`–`256`. | | `GH_TOKEN` | Authentication token. Takes precedence over `GITHUB_TOKEN`. | | `GITHUB_TOKEN` | Authentication token. | | `USE_BUILTIN_RIPGREP` | Set to `false` to use the system ripgrep instead of the bundled version. | @@ -850,6 +857,35 @@ If multiple hooks of the same type are configured, they execute in order. For `p MCP servers provide additional tools to the CLI agent. Configure persistent servers in `~/.copilot/mcp-config.json`. Use `--additional-mcp-config` to add servers for a single session. +### `copilot mcp` subcommand + +Use `copilot mcp` to manage MCP server configurations from the command line without starting an interactive session. + +| Subcommand | Description | +|------------|-------------| +| `list [--json]` | List all configured MCP servers grouped by source. | +| `get [--json]` | Show configuration and tools for a specific server. | +| `add ` | Add a server to the user configuration. Writes to `~/.copilot/mcp-config.json`. | +| `remove ` | Remove a user-level server. Workspace servers must be edited in their configuration files directly. | + +**`copilot mcp add` options:** + +| Option | Description | +|--------|-------------| +| `-- [args...]` | Command and arguments for local (stdio) servers. | +| `--url ` | URL for remote servers. | +| `--type ` | Transport type: `local`, `stdio`, `http`, or `sse`. | +| `--env KEY=VALUE` | Environment variable (repeatable). | +| `--header KEY=VALUE` | HTTP header for remote servers (repeatable). | +| `--tools ` | Tool filter: `"*"` for all, a comma-separated list, or `""` for none. | +| `--timeout ` | Timeout in milliseconds. | +| `--json` | Output added configuration as JSON. | +| `--show-secrets` | Show full environment variable and header values. | +| `--config-dir ` | Path to the configuration directory. | + +> [!CAUTION] +> `--show-secrets` can print sensitive environment variable and header values to your terminal or logs. Only use this option in trusted environments, and avoid copying, pasting, or otherwise capturing the output in shared logs or history. + ### Transport types | Type | Description | Required fields | @@ -918,8 +954,7 @@ MCP servers are loaded from multiple sources, each with a different trust level. |--------|-------------|----------------| | Built-in | High | No | | Repository (`.github/mcp.json`) | Medium | Recommended | -| Workspace (`.mcp.json`, `.vscode/mcp.json`) | Medium | Recommended | -| Dev Container (`.devcontainer/devcontainer.json`) | Medium | Recommended | +| Workspace (`.mcp.json`) | Medium | Recommended | | User config (`~/.copilot/mcp-config.json`) | User-defined | User responsibility | | Remote servers | Low | Always | @@ -969,7 +1004,7 @@ Custom agents are specialized AI agents defined in Markdown files. The filename | Agent | Default model | Description | |-------|--------------|-------------| | `code-review` | claude-sonnet-4.5 | High signal-to-noise code review. Analyzes diffs for bugs, security issues, and logic errors. | -| `critic` | complementary model | Rubber-duck adversarial feedback on proposals, designs, and implementations. Identifies weak points and suggests improvements. Available for Claude models. Experimental—requires `--experimental`. | +| `rubber-duck` | complementary model | Use a complementary model to provide a constructive critique of proposals, designs, implementations, or tests. Identifies weak points and suggests improvements. Only available in experimental mode. | | `explore` | claude-haiku-4.5 | Fast codebase exploration. Searches files, reads code, and answers questions. Returns focused answers under 300 words. Safe to run in parallel. | | `general-purpose` | claude-sonnet-4.5 | Full-capability agent for complex multi-step tasks. Runs in a separate context window. | | `research` | claude-sonnet-4.6 | Deep research agent. Generates a report based on information in your codebase, in relevant repositories, and on the web. | @@ -996,6 +1031,17 @@ Custom agents are specialized AI agents defined in Markdown files. The filename Project-level agents take precedence over user-level agents. Plugin agents have the lowest priority. +### Subagent limits + +The CLI enforces depth and concurrency limits to prevent runaway agent spawning. + +| Limit | Default | Environment variable | +|-------|---------|---------------------| +| Max depth | `6` | `COPILOT_SUBAGENT_MAX_DEPTH` | +| Max concurrent | `32` | `COPILOT_SUBAGENT_MAX_CONCURRENT` | + +**Depth** counts how many agents are nested within one another. When the depth limit is reached, the innermost agent cannot spawn further subagents. **Concurrency** counts how many subagents are running simultaneously across the entire session tree. When the limit is reached, new subagent requests are rejected until an active agent completes. Values are clamped between `1` and `256`. + ## Permission approval responses When the CLI prompts for permission to execute an operation, you can respond with the following keys. @@ -1188,7 +1234,7 @@ Feature flags enable functionality that is not yet generally available. Enable f | Flag | Tier | Description | |------|------|-------------| -| `RUBBER_DUCK_AGENT` | experimental | Rubber-duck subagent for adversarial feedback on code and designs (available for Claude models) | +| `RUBBER_DUCK_AGENT` | experimental | Rubber-duck subagent for adversarial feedback on code and designs | | `BACKGROUND_SESSIONS` | experimental | Multiple concurrent sessions with background management | | `MULTI_TURN_AGENTS` | experimental | Multi-turn subagent message passing via `write_agent` | | `EXTENSIONS` | experimental | Programmatic extensions with custom tools and hooks | diff --git a/content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md b/content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md index e69adc92a007..8cf199f38fae 100644 --- a/content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md +++ b/content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md @@ -75,7 +75,7 @@ For a full list of configuration settings, enter `copilot help config` in your t ### `mcp-config.json` -Defines MCP (Model Context Protocol) servers available at the user level. These servers are available in all your sessions, regardless of which project directory you're in. Project-level MCP configurations (in `.mcp.json`, `.github/mcp.json`, or `.vscode/mcp.json`) take precedence over user-level definitions when server names conflict. +Defines MCP (Model Context Protocol) servers available at the user level. These servers are available in all your sessions, regardless of which project directory you're in. Project-level MCP configurations (in `.mcp.json` or `.github/mcp.json`) take precedence over user-level definitions when server names conflict. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers). diff --git a/content/copilot/reference/copilot-cli-reference/cli-plugin-reference.md b/content/copilot/reference/copilot-cli-reference/cli-plugin-reference.md index 69238166dfae..0b682dc64dda 100644 --- a/content/copilot/reference/copilot-cli-reference/cli-plugin-reference.md +++ b/content/copilot/reference/copilot-cli-reference/cli-plugin-reference.md @@ -146,9 +146,9 @@ For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-cop | Marketplace manifest | `marketplace.json`, `.plugin/marketplace.json`, `.github/plugin/marketplace.json`, or `.claude-plugin/marketplace.json` (checked in this order) | | Agents | `agents/` (default, overridable in manifest) | | Skills | `skills/` (default, overridable in manifest) | -| Hooks config | `hooks.json` or `hooks/hooks.json` | -| MCP config | `.mcp.json`, `.vscode/mcp.json`, `.devcontainer/devcontainer.json`, `.github/mcp.json` | -| LSP config | `lsp.json` or `.github/lsp.json` | +| Hooks configuration | `hooks.json` or `hooks/hooks.json` | +| MCP configuration | `.mcp.json`, `.github/mcp.json` | +| LSP configuration | `lsp.json` or `.github/lsp.json` | ## Loading order and precedence @@ -202,9 +202,8 @@ The following diagram illustrates the loading order and precedence rules. ┌──────────────────────▼──────────────────────────────────────────────┐ │ MCP SERVERS - LAST LOADED IS USED (dedup by server name) │ │ 1. ~/.copilot/mcp-config.json (lowest priority) │ - │ 2. .vscode/mcp.json (workspace) │ - │ 3. PLUGIN: MCP configs (plugins) │ - │ 4. --additional-mcp-config flag (highest priority) │ + │ 2. PLUGIN: MCP configs (plugins) │ + │ 3. --additional-mcp-config flag (highest priority) │ └─────────────────────────────────────────────────────────────────────┘ ``` diff --git a/data/reusables/cli/public-preview-remote-access.md b/data/reusables/cli/public-preview-remote-access.md new file mode 100644 index 000000000000..bd590c6c8371 --- /dev/null +++ b/data/reusables/cli/public-preview-remote-access.md @@ -0,0 +1,3 @@ +> [!NOTE] +> * Remote access to {% data variables.copilot.copilot_cli_short %} sessions is in {% data variables.release-phases.public_preview %} and subject to change. +> * Mobile access is currently only available in the latest beta release of {% data variables.product.prodname_mobile %}. You can join the test program for {% data variables.product.prodname_mobile %} via [Apple TestFlight for iOS](https://testflight.apple.com/join/NLskzwi5) and [Google Play for Android](https://play.google.com/apps/testing/com.github.android). diff --git a/data/reusables/cli/remote-access-slash-commands.md b/data/reusables/cli/remote-access-slash-commands.md new file mode 100644 index 000000000000..e8bd98cb31fe --- /dev/null +++ b/data/reusables/cli/remote-access-slash-commands.md @@ -0,0 +1,2 @@ +> [!NOTE] +> Slash commands—such as `/allow-all`—are not currently available from the remote interface. diff --git a/data/reusables/dependabot/where-to-view-dependabot-alerts.md b/data/reusables/dependabot/where-to-view-dependabot-alerts.md index 30bcdbc721d3..f4e5dada67a3 100644 --- a/data/reusables/dependabot/where-to-view-dependabot-alerts.md +++ b/data/reusables/dependabot/where-to-view-dependabot-alerts.md @@ -1 +1 @@ -You can view all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %} in your repository's {% data variables.product.prodname_dependabot_alerts %} tab. +You can view all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %} in your repository's {% data variables.product.prodname_dependabot %} tab. diff --git a/data/variables/secret-scanning.yml b/data/variables/secret-scanning.yml index 4c558333c338..795923ac6605 100644 --- a/data/variables/secret-scanning.yml +++ b/data/variables/secret-scanning.yml @@ -17,9 +17,9 @@ roi-calculator: 'ROI calculator' pricing-calculator: 'pricing calculator' # Secret risk assessment call to action links. If changing the links below, also update the hard-coded link in /code-security/index.md -secret-risk-assessment-cta-link: '/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/assess-your-secret-risk' -secret-risk-assessment-cta-text: 'Find out how to run a free secret risk assessment' -secret-risk-assessment-cta-product: '[{% data variables.secret-scanning.secret-risk-assessment-cta-text %}](/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/assess-your-secret-risk#generating-an-initial-secret-risk-assessment)' +secret-risk-assessment-cta-link: 'https://github.com/get_started?with=risk-assessment' +secret-risk-assessment-cta-text: 'Run a security risk assessment' +secret-risk-assessment-cta-product: '[{% data variables.secret-scanning.secret-risk-assessment-cta-text %}](https://github.com/get_started?with=risk-assessment)' # Combined to provide a secret to demonstrate push protection. Dummy secret, no access. learner-example-secret-a: 'secret_scanning_ab85fc6f8d76' diff --git a/src/content-pipelines/state/copilot-cli.sha b/src/content-pipelines/state/copilot-cli.sha index b1910ad011c5..dbf211204f02 100644 --- a/src/content-pipelines/state/copilot-cli.sha +++ b/src/content-pipelines/state/copilot-cli.sha @@ -1 +1 @@ -ed524424679cf44e46cf94e5beb5b8aa9974b554 +36e4da8c7502ef8fc3f3380182cd7ea164365662 diff --git a/src/github-apps/lib/config.json b/src/github-apps/lib/config.json index 57c709aa468e..190099ed7cf3 100644 --- a/src/github-apps/lib/config.json +++ b/src/github-apps/lib/config.json @@ -60,5 +60,5 @@ "2022-11-28" ] }, - "sha": "36e6d2087a74bda6b56e450420eee3427798bc75" + "sha": "3ba1e7273bb94c613cf608640e4a7a860310669b" } \ No newline at end of file diff --git a/src/rest/data/fpt-2022-11-28/commits.json b/src/rest/data/fpt-2022-11-28/commits.json index 2700734c765a..cd6016387f9d 100644 --- a/src/rest/data/fpt-2022-11-28/commits.json +++ b/src/rest/data/fpt-2022-11-28/commits.json @@ -4545,7 +4545,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5172,6 +5172,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5272,7 +5332,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7234,6 +7294,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/fpt-2026-03-10/commits.json b/src/rest/data/fpt-2026-03-10/commits.json index 390d232b86c3..8bce13fed123 100644 --- a/src/rest/data/fpt-2026-03-10/commits.json +++ b/src/rest/data/fpt-2026-03-10/commits.json @@ -4387,7 +4387,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5014,6 +5014,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5114,7 +5174,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7076,6 +7136,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghec-2022-11-28/commits.json b/src/rest/data/ghec-2022-11-28/commits.json index fbed91baf344..989c41f6e357 100644 --- a/src/rest/data/ghec-2022-11-28/commits.json +++ b/src/rest/data/ghec-2022-11-28/commits.json @@ -4545,7 +4545,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5172,6 +5172,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5272,7 +5332,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7234,6 +7294,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghec-2026-03-10/commits.json b/src/rest/data/ghec-2026-03-10/commits.json index 903376320491..9be925a2202d 100644 --- a/src/rest/data/ghec-2026-03-10/commits.json +++ b/src/rest/data/ghec-2026-03-10/commits.json @@ -4387,7 +4387,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5014,6 +5014,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5114,7 +5174,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7076,6 +7136,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.14-2022-11-28/commits.json b/src/rest/data/ghes-3.14-2022-11-28/commits.json index d0937249f2bf..bc100e3808c7 100644 --- a/src/rest/data/ghes-3.14-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.14-2022-11-28/commits.json @@ -4537,7 +4537,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5154,6 +5154,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5254,7 +5314,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7188,6 +7248,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.15-2022-11-28/commits.json b/src/rest/data/ghes-3.15-2022-11-28/commits.json index 9474ce08764b..c9ec4346205f 100644 --- a/src/rest/data/ghes-3.15-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.15-2022-11-28/commits.json @@ -4537,7 +4537,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5154,6 +5154,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5254,7 +5314,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7188,6 +7248,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.16-2022-11-28/commits.json b/src/rest/data/ghes-3.16-2022-11-28/commits.json index cd25393cc1b7..652e6f36cba7 100644 --- a/src/rest/data/ghes-3.16-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.16-2022-11-28/commits.json @@ -4537,7 +4537,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5154,6 +5154,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5254,7 +5314,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7188,6 +7248,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.17-2022-11-28/commits.json b/src/rest/data/ghes-3.17-2022-11-28/commits.json index 991d0c9d67df..83b1ca40fcf0 100644 --- a/src/rest/data/ghes-3.17-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.17-2022-11-28/commits.json @@ -4545,7 +4545,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5172,6 +5172,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5272,7 +5332,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7234,6 +7294,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.18-2022-11-28/commits.json b/src/rest/data/ghes-3.18-2022-11-28/commits.json index 3d8bf8337fd1..cba70fafd94f 100644 --- a/src/rest/data/ghes-3.18-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.18-2022-11-28/commits.json @@ -4545,7 +4545,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5172,6 +5172,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5272,7 +5332,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7234,6 +7294,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.19-2022-11-28/commits.json b/src/rest/data/ghes-3.19-2022-11-28/commits.json index 6df7074e3d65..f0c9a9b5fe46 100644 --- a/src/rest/data/ghes-3.19-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.19-2022-11-28/commits.json @@ -4545,7 +4545,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5172,6 +5172,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5272,7 +5332,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7234,6 +7294,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/data/ghes-3.20-2022-11-28/commits.json b/src/rest/data/ghes-3.20-2022-11-28/commits.json index 8aabb589a079..a9c33b766d8e 100644 --- a/src/rest/data/ghes-3.20-2022-11-28/commits.json +++ b/src/rest/data/ghes-3.20-2022-11-28/commits.json @@ -4545,7 +4545,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -5172,6 +5172,66 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 4: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "ref": "REF" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.sha", + "description": "

Response

", + "example": "ac3282a2725be3b1d4979169a7a311c89066af1c", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ @@ -5272,7 +5332,7 @@ "codeExamples": [ { "request": { - "description": "Example", + "description": "Example 1: Status Code 200", "acceptHeader": "application/vnd.github.v3+json", "parameters": { "owner": "OWNER", @@ -7234,6 +7294,46 @@ ] } } + }, + { + "request": { + "description": "Example 2: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.diff", + "description": "

Response

", + "example": "diff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } + }, + { + "request": { + "description": "Example 3: Status Code 200", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "owner": "OWNER", + "repo": "REPO", + "basehead": "BASEHEAD" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/vnd.github.patch", + "description": "

Response

", + "example": "From ac3282a2725be3b1d4979169a7a311c89066af1c Mon Sep 17 00:00:00 2001\nFrom: Mona Lisa <87831417+monalisa@users.noreply.github.com>\nDate: Fri, 6 Mar 2026 11:18:45 +0000\nSubject: [PATCH] Change 'test' to 'test change' in testfile\n\n---\ntestfile | 2 +-\n1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/testfile b/testfile\nindex 9bdeaeb..912c7ef 100644\n--- a/testfile\n+++ b/testfile\n@@ -1 +1 @@\n-test\n+test change\n", + "schema": { + "type": "string" + } + } } ], "statusCodes": [ diff --git a/src/rest/lib/config.json b/src/rest/lib/config.json index da35b74eaa59..308c251477c8 100644 --- a/src/rest/lib/config.json +++ b/src/rest/lib/config.json @@ -55,5 +55,5 @@ ] } }, - "sha": "36e6d2087a74bda6b56e450420eee3427798bc75" + "sha": "3ba1e7273bb94c613cf608640e4a7a860310669b" } \ No newline at end of file diff --git a/src/webhooks/lib/config.json b/src/webhooks/lib/config.json index ad671ef70bdd..21d837b367b1 100644 --- a/src/webhooks/lib/config.json +++ b/src/webhooks/lib/config.json @@ -1,3 +1,3 @@ { - "sha": "36e6d2087a74bda6b56e450420eee3427798bc75" + "sha": "3ba1e7273bb94c613cf608640e4a7a860310669b" } \ No newline at end of file