Delete orphaned files (2025-06-23-16-29) (#56229)
Co-authored-by: hubwriter <hubwriter@github.com>
This commit is contained in:
docs-bot
Binary file not shown.
|
Before Width: | Height: | Size: 133 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 161 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 116 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 96 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 26 KiB |
@@ -1 +0,0 @@
|
||||
You can set a specific spending limit or, for some accounts, allow unlimited spending. The spending limit applies to your combined overages (any usage beyond the amounts included with your plan) for {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}.
|
||||
@@ -1,6 +0,0 @@
|
||||
1. Click **Budgets and alerts**.
|
||||
1. Click **New budget**.
|
||||
1. Under "Budget Type" select either **Product-level budget** or **SKU-level budget**.
|
||||
* To create a Product-level budget, choose a metered product from the dropdown.
|
||||
* To create a SKU-level budget, choose a SKU from the dropdown. This limits spending for an individual SKU.
|
||||
1. Under "Budget scope", set the scope of spending for this budget.
|
||||
@@ -1,3 +0,0 @@
|
||||
Email notifications are sent to account owners and billing managers when spending reaches 75%, 90% and 100% of your account's included usage and when spending reaches 75%, 90%, and 100% of your account's spending limit.
|
||||
|
||||
You can disable these notifications at any time by navigating to the "Email alerts" section at the bottom of the "Spending limit" page.
|
||||
@@ -1 +0,0 @@
|
||||
1. Under "Codespaces", either select **Limit spending** and enter a spending limit, or select **Unlimited spending**.
|
||||
@@ -1,2 +0,0 @@
|
||||
> [!NOTE]
|
||||
> {% data variables.copilot.copilot_claude_opus %} in {% data variables.copilot.copilot_chat_short %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
|
||||
@@ -1,2 +0,0 @@
|
||||
> [!NOTE]
|
||||
> {% data variables.copilot.copilot_claude_opus %} and {% data variables.copilot.copilot_claude_sonnet_40 %} in {% data variables.copilot.copilot_chat_short %} are currently in {% data variables.release-phases.public_preview %} and subject to change.
|
||||
@@ -1,2 +0,0 @@
|
||||
> [!NOTE]
|
||||
> {% data variables.copilot.copilot_claude_sonnet_40 %} in {% data variables.copilot.copilot_chat_short %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
|
||||
@@ -1,2 +0,0 @@
|
||||
> [!NOTE]
|
||||
> {% data variables.copilot.copilot_gemini_25_pro %} in {% data variables.copilot.copilot_chat_short %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
|
||||
@@ -1 +0,0 @@
|
||||
For information about the capabilities of {% data variables.copilot.copilot_gemini %}, see the [Google for developers blog](https://developers.googleblog.com/en/gemini-2-5-flash-pro-live-api-veo-2-gemini-api/) and the [Google Cloud documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/models). For details of Google's data handling policy, see [Generative AI and data governance](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance#prediction) on the Google website.
|
||||
@@ -1,3 +0,0 @@
|
||||
{% data variables.copilot.copilot_gemini_25_pro %} is well-suited for advanced coding tasks, such as developing complex algorithms or debugging intricate codebases.
|
||||
It can assist with scientific research by analyzing data and generating insights across a wide range of disciplines. Its long-context capabilities allow it to manage and understand extensive documents or datasets effectively.
|
||||
{% data variables.copilot.copilot_gemini_25_pro %} is a strong choice for developers needing a powerful model.
|
||||
@@ -1 +0,0 @@
|
||||
{% data variables.copilot.copilot_gpt_41 %} is a revamped version of OpenAI's {% data variables.copilot.copilot_gpt_4o %} model. This model is a strong default choice for common development tasks that benefit from speed, responsiveness, and general-purpose reasoning. If you're working on tasks that require broad knowledge, fast iteration, or basic code understanding, {% data variables.copilot.copilot_gpt_41 %} makes large improvements over {% data variables.copilot.copilot_gpt_4o %}.
|
||||
@@ -1 +0,0 @@
|
||||
GPT-4.5 is a good choice for tasks that involve multiple steps, require deeper code comprehension, or benefit from a conversational model that handles nuance well.
|
||||
@@ -1,2 +0,0 @@
|
||||
o1 is a good choice for tasks that require deep logical reasoning. Its ability to reason through complex logic enables {% data variables.product.prodname_copilot_short %} to break down problems into clear, actionable steps.
|
||||
This makes o1 particularly well-suited for debugging. Its internal reasoning can extend beyond the original prompt to explore the broader context of a problem and can uncover edge cases or root causes that weren’t explicitly mentioned.
|
||||
@@ -1 +0,0 @@
|
||||
o3-mini is a good choice for developers who need fast, reliable answers to simple or repetitive coding questions. Its speed and efficiency make it ideal for lightweight development tasks.
|
||||
@@ -1,2 +0,0 @@
|
||||
{% data variables.copilot.copilot_o3 %} is a good choice for tasks that require deep logical reasoning. Its ability to reason through complex logic enables {% data variables.product.prodname_copilot_short %} to break down problems into clear, actionable steps.
|
||||
This makes {% data variables.copilot.copilot_o3 %} particularly well-suited for debugging. Its internal reasoning can extend beyond the original prompt to explore the broader context of a problem and can uncover edge cases or root causes that weren’t explicitly mentioned.
|
||||
@@ -1 +0,0 @@
|
||||
{% data variables.copilot.copilot_o4_mini %} is a good choice for developers who need fast, reliable answers to simple or repetitive coding questions. Its speed and efficiency make it ideal for lightweight development tasks.
|
||||
@@ -1,2 +0,0 @@
|
||||
> [!NOTE]
|
||||
> {% data variables.copilot.copilot_o3 %} in {% data variables.copilot.copilot_chat_short %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
|
||||
@@ -1,2 +0,0 @@
|
||||
> [!NOTE]
|
||||
> {% data variables.copilot.copilot_o4_mini %} in {% data variables.copilot.copilot_chat_short %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
|
||||
@@ -1,5 +0,0 @@
|
||||
> [!IMPORTANT]
|
||||
> Certain requests may experience rate limits.
|
||||
>
|
||||
> * Rate limits restrict the number of requests that can be made within a specific time period.
|
||||
> * High demand may result in rate limiting.
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Actions usage data.
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Actions usage data.
|
||||
@@ -1,6 +0,0 @@
|
||||
1. Under **Billing and licensing**, click **Usage**.
|
||||
1. To display only Actions usage within the graph, click the search bar, then click **Product**. Within the list of products that generates, click **Actions**.
|
||||
1. To further filter the usage graph, use the dropdown menus:
|
||||
* To view usage by SKU, select the **Group** dropdown, then click **SKU**.
|
||||
* To filter by time, select **Time Frame**, then click a time period.
|
||||
* Below the graph, you can see a more granular overview of the usage. Click the arrow next to a specific date to see a nested table with usage per SKU, units, price/unit, gross amount (the amount actually used), and billed amount (the amount you are charged).
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Codespaces usage data.
|
||||
@@ -1,6 +0,0 @@
|
||||
1. Under **Billing and licensing**, click **Usage**.
|
||||
1. To display only Codespaces usage within the graph, click the search bar, then click **Product**. Within the list of products that generates, click **Codespaces**.
|
||||
1. To further filter the usage graph, use the dropdown menus:
|
||||
* To view usage by SKU, select the **Group** dropdown, then click **SKU**.
|
||||
* To filter by time, select **Time Frame**, then click a time period.
|
||||
* Below the graph, you can see a more granular overview of the usage. Click the arrow next to a specific date to see a nested table with usage per SKU, units, price/unit, gross amount (the amount actually used), and billed amount (the amount you are charged).
|
||||
@@ -1,3 +0,0 @@
|
||||
1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**.
|
||||
|
||||
|
||||
@@ -1,2 +0,0 @@
|
||||
1. Under "{% data variables.large_files.product_name_short %} Data", view details of your bandwidth and storage usage.
|
||||
1. Optionally, to view your account's LFS data usage by repository, select **Storage** or **Bandwidth**.
|
||||
@@ -1 +0,0 @@
|
||||
1. Next to "{% data variables.large_files.product_name_short %} Data", select the **Edit** dropdown menu and click **Remove data packs**.
|
||||
@@ -1,3 +0,0 @@
|
||||
1. At the top of the page, under "Payment information," click **Manage spending limit**.
|
||||
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
1. Scroll down to "Actions & Packages" and choose to limit spending or allow unlimited spending.
|
||||
@@ -1 +0,0 @@
|
||||
1. Under "Actions & Packages", choose to limit spending or allow unlimited spending.
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Packages usage data.
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Packages usage data.
|
||||
@@ -1,6 +0,0 @@
|
||||
1. Under **Billing and licensing**, click **Usage**.
|
||||
1. To display only Packages usage in the graph, click the search bar, then click **Product**. Within the list of products that generates, click **Packages**.
|
||||
1. To further filter the usage graph, use the dropdown menus:
|
||||
* To view usage by SKU, select the **Group** dropdown, then click **SKU**.
|
||||
* To filter by time, select **Time Frame**, then click a time period.
|
||||
* Below the graph, you can see a more granular overview of the usage. Click the arrow next to a specific date to see a nested table with usage per SKU, units, price/unit, gross amount (the amount actually used), and billed amount (the amount you are charged).
|
||||
@@ -1 +0,0 @@
|
||||
1. Depending on which option you chose, click either **Update limit** or **Update to unlimited**.
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Actions usage data.
|
||||
@@ -1 +0,0 @@
|
||||
1. Optionally, above the usage graph, click **Get usage report** and select the desired timeframe to generate a CSV report of your usage. This report will include Packages usage data.
|
||||
@@ -1 +0,0 @@
|
||||
Unused bandwidth doesn't roll over month-to-month.
|
||||
@@ -1,4 +0,0 @@
|
||||
1. Under "Downgrade data plan", select the number of data packs you'd like to downgrade to.
|
||||
|
||||
|
||||
1. To finish downgrading, click **Downgrade data plan**.
|
||||
@@ -1 +0,0 @@
|
||||
1. To confirm your new monthly data pack quantity, click **Purchase**.
|
||||
@@ -1,2 +0,0 @@
|
||||
1. Enter the number of data packs you want to add to your account. Each pack costs {% data variables.large_files.pack_monthly_price %}, and provides {% data variables.large_files.pack_monthly_bandwidth %} of bandwidth and {% data variables.large_files.pack_monthly_storage %} for storage.
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
{% data reusables.package_registry.packages-spending-limit-brief %}
|
||||
|
||||
If you have an unlimited spending limit or a spending limit set higher than $0 USD, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Any coupons on your account do not apply to {% data variables.product.prodname_registry %} overages.
|
||||
|
||||
{% data reusables.billing.overages-billed-monthly %}
|
||||
@@ -1 +0,0 @@
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**, then click **Spending limits**.
|
||||
Reference in New Issue
Block a user