Repo sync

content/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs.md

@@ -17,12 +17,9 @@ category:
 contentType: how-tos
 ---
 
-> [!NOTE]
-> Re-run workflows use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. The workflow will also use the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (git ref) of the original event that triggered the workflow run.
-{% ifversion fpt or ghec %}
-> 
-> A workflow run can be re-run a maximum of 50 times. Re-running only a single job or failed jobs counts towards this limit.
-{% endif %}
+Re-runs use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. The workflow will also use the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (git ref) of the original event that triggered the workflow run.
+
+A workflow run can be re-run a maximum of 50 times. This limit includes both full re-runs and re-runs of a subset of jobs.
 
 ## Re-running all the jobs in a workflow
 

content/actions/reference/limits.md

@@ -28,9 +28,10 @@ These limits are subject to change.
 | :---- | :---- | :---- | :---- | :---- |
 | Workflow execution limit | Workflow run time | 35 days / workflow run | If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval. | {% octicon "x" aria-label="No" %} |
 | Workflow execution limit | Gate approval time | 30 days | A workflow may wait for up to [30 days on environment approvals](/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment#wait-timer). | {% octicon "x" aria-label="No" %} |
+| Workflow execution limit | Job Matrix | 256 jobs / workflow run | A job matrix can generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.github %}-hosted and self-hosted runners. | {% octicon "x" aria-label="No" %} |
+| Workflow execution limit | Re-run | 50 re-runs | A workflow run can be re-run a maximum of 50 times. This limit includes both full re-runs and re-runs of a subset of jobs. | {% octicon "check" aria-label="Yes" %} Support ticket |
 | Workflows queuing | Workflow trigger event rate limit | 1500 events / 10 seconds / repository | Each repository is limited to events triggering a workflow run. | {% octicon "check" aria-label="Yes" %} Support ticket |
 | Workflows queuing | Workflow run queued | 500 workflow runs / 10 seconds | When the limit is reached, the workflow runs that were supposed to be triggered by the webhook events will be blocked and will not be queued. Reusable workflows are viewed as a single entity. For example, a run with 30 reusable workflows counts as 1 in this instance. | {% octicon "x" aria-label="No" %} |
-| Workflow execution | Job Matrix | 256 jobs / workflow run | A job matrix can generate a maximum of jobs per workflow run. This limit applies to both {% data variables.product.github %}-hosted and self-hosted runners. | {% octicon "x" aria-label="No" %} |
 | Self-hosted | Runner registrations | 1500 runners / 5 minutes / repository/org/enterprise | Runners can be registered per repository/organization/enterprise. | {% octicon "check" aria-label="Yes" %} Support ticket |
 | Self-hosted | Runners per runner group | 10,000 runners | Runners registered at the same time per runner group. | {% octicon "x" aria-label="No" %} |
 | Self-hosted | Job execution time | 5 days | Each job in a workflow can run for up to 5 days of execution time. If a job reaches this limit, the job is terminated and fails. | {% octicon "x" aria-label="No" %} |

content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/controlling-dependencies-updated.md

@@ -133,7 +133,7 @@ For more information, see `allow` in [AUTOTITLE](/code-security/dependabot/worki
 By default, {% data variables.product.prodname_dependabot %} creates version update pull requests only for the dependencies that are explicitly defined in a manifest (`direct` dependencies). This configuration uses `allow` to tell {% data variables.product.prodname_dependabot %} that we want it to maintain `all` types of dependency. That is, both the `direct` dependencies and their dependencies (also known as indirect dependencies, sub-dependencies, or transient dependencies). In addition, the configuration tells {% data variables.product.prodname_dependabot %} to ignore all dependencies with a name matching the pattern `org.xwiki.*` because we have a different process for maintaining them.
 
 > [!TIP]
-> {% data variables.product.prodname_dependabot %} checks for all **allowed** dependencies, then filters out any **ignored** dependencies. If a dependency is matched by an **allow** and an **ignore** statement, then it is ignored.
+> {% data variables.product.prodname_dependabot %} checks for all **allowed** dependencies, then filters out any **ignored** dependencies. If a dependency is matched by an **allow** and an **ignore** statement, then it is ignored.{% ifversion dependabot-allow-update-types %} You can also use `update-types` in `allow` rules to restrict updates to specific semantic versioning levels.{% endif %}
 
 ```yaml copy
 version: 2
@@ -167,6 +167,58 @@ updates:
     open-pull-requests-limit: 15
 ```
 
+{% ifversion dependabot-allow-update-types %}
+
+## Allowing specific semantic versioning levels for updates
+
+You can use `update-types` with `allow` to restrict updates to specific semantic versioning (SemVer) levels. This is useful when you want to be explicit about which types of updates Dependabot should create pull requests for.
+
+> [!NOTE]
+> `update-types` only affects _version_ updates, not _security_ updates. Security updates will always be created regardless of the `update-types` setting.
+
+For more information, see `update-types` in [AUTOTITLE](/code-security/dependabot/working-with-dependabot/dependabot-options-reference#update-types-allow).
+
+Here are some examples showing how `update-types` can be used with `allow`.
+
+* To allow only minor and patch updates for a specific dependency, you can combine `update-types` with `dependency-name`.
+
+   ```yaml copy
+   version: 2
+   updates:
+     - package-ecosystem: "maven"
+       directory: "/"
+       schedule:
+         interval: "weekly"
+       allow:
+         - dependency-name: "io.micrometer:micrometer-core"
+           update-types:
+             - "version-update:semver-minor"
+             - "version-update:semver-patch"
+   ```
+
+* To apply different update policies for production and development dependencies, you can combine `update-types` with `dependency-type`.
+
+   ```yaml copy
+   version: 2
+   updates:
+     - package-ecosystem: "composer"
+       directory: "/"
+       schedule:
+         interval: "monthly"
+       allow:
+         - dependency-type: "production"
+           update-types:
+             - "version-update:semver-patch"
+         - dependency-type: "development"
+           update-types:
+             - "version-update:semver-minor"
+             - "version-update:semver-patch
+   ```
+
+  In this example, production dependencies will only receive patch updates, while development dependencies will receive both minor and patch updates.
+
+{% endif %}
+
 ## Ignoring specific versions or ranges of versions
 
 You can use `versions` in conjunction with `ignore` to ignore specific versions or ranges of versions.
@@ -201,7 +253,8 @@ For more information, see `versions` in [AUTOTITLE](/code-security/dependabot/wo
 
 ## Specifying the semantic versioning level to ignore
 
-You can specify one or more semantic versioning (SemVer) levels to ignore using `update-types`.
+
+You can specify one or more semantic versioning (SemVer) levels to ignore using `update-types` with `ignore`.{% ifversion dependabot-allow-update-types %} Alternatively, you can use `update-types` with `allow` to explicitly specify which update levels to allow, see [Allowing specific semantic versioning levels for updates](#allowing-specific-semantic-versioning-levels-for-updates).{% endif %}
 
 For more information, see `update-types` in [AUTOTITLE](/code-security/dependabot/working-with-dependabot/dependabot-options-reference#update-types-ignore).
 

content/code-security/reference/supply-chain-security/dependabot-options-reference.md

@@ -81,6 +81,9 @@ When `allow` is specified {% data variables.product.prodname_dependabot %} uses
 |------------|---------|
 | `dependency-name` | Allow updates for dependencies with matching names, optionally using `*` to match zero or more characters. |
 | `dependency-type` | Allow updates for dependencies of specific types. |
+| {% ifversion dependabot-allow-update-types %} |
+| `update-types` | Allow updates to one or more semantic versioning levels. Supported values: `version-update:semver-patch`, `version-update:semver-minor`, and `version-update:semver-major`. |
+| {% endif %} |
 
 ### `dependency-name` (`allow`)
 
@@ -101,6 +104,26 @@ For most package managers, you should define a value that will match the depende
 | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip`{% ifversion dependabot-uv-support %}, `uv`{% endif %} (not all managers) | Only to dependencies defined by the package manager as production dependencies. |
 | `development`| `bundler`, `composer`, `mix`, `maven`, `npm`, `pip`{% ifversion dependabot-uv-support %}, `uv`{% endif %} (not all managers) | Only to dependencies defined by the package manager as development dependencies. |
 
+{% ifversion dependabot-allow-update-types %}
+
+### `update-types` (`allow`)
+
+`update-types` only affects _version_ updates, not _security updates_.
+
+Specify which semantic versions (SemVer) to allow.
+
+SemVer is an accepted standard for defining versions of software packages, in the form `x.y.z`. {% data variables.product.prodname_dependabot %} assumes that versions in this form are always `major.minor.patch`. The `update-types` value is a list of one or more strings.
+
+* Use `version-update:semver-patch` to allow patch releases.
+* Use `version-update:semver-minor` to allow minor releases.
+* Use `version-update:semver-major` to allow major releases.
+
+When `update-types` is omitted from an `allow` rule, all update types are allowed for that rule.
+
+You can combine `update-types` with `dependency-name` or `dependency-type` to further narrow allowed updates. For examples of how you can combine these options, see [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/controlling-dependencies-updated#allowing-specific-semantic-versioning-levels-for-updates).
+
+{% endif %}
+
 ## `assignees` {% octicon "versions" aria-label="Version updates" height="24" %} {% octicon "shield-check" aria-label="Security updates" height="24" %}
 
 Specify individual assignees for all pull requests raised for a package ecosystem.  For examples, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/customizing-dependabot-prs).
@@ -351,7 +374,7 @@ When `ignore` is used {% data variables.product.prodname_dependabot %} uses the
 |------------|---------|
 | `dependency-name` | Ignore updates for dependencies with matching names, optionally using `*` to match zero or more characters. |
 | `versions` | Ignore specific versions or ranges of versions. |
-| `update-types` | Ignore updates to one or more semantic versioning levels. Supported values: `version-update:semver-minor`, `version-update:semver-patch`, and `version-update:semver-major`. |
+| `update-types` | Ignore updates to one or more semantic versioning levels. Supported values: `version-update:semver-patch`, `version-update:semver-minor`, and `version-update:semver-major`. |
 
 ### `dependency-name` (`ignore`)
 

content/copilot/concepts/agents/copilot-cli/about-cli-plugins.md

@@ -10,6 +10,8 @@ contentType: concepts
 category:
   - Learn about Copilot # Copilot discovery page
   - Learn about Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 Plugins provide a way to distribute custom CLI functionality. You can use a plugin to add a preconfigured set of capabilities to {% data variables.copilot.copilot_cli_short %}.

content/copilot/concepts/agents/copilot-cli/about-copilot-cli.md

@@ -12,6 +12,8 @@ category:
   - Learn about Copilot CLI # Copilot CLI bespoke page
 redirect_from:
   - /copilot/concepts/agents/about-copilot-cli
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/concepts/agents/copilot-cli/about-custom-agents.md

@@ -7,6 +7,8 @@ versions:
 category:
   - Learn about Copilot
 contentType: concepts
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 {% data reusables.copilot.copilot-cli.custom-agents-about-intro %}

content/copilot/concepts/agents/copilot-cli/autopilot.md

@@ -9,6 +9,8 @@ contentType: concepts
 category:
   - Learn about Copilot CLI # Copilot CLI bespoke page
   - Learn about Copilot # Copilot discovery page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Overview

content/copilot/concepts/agents/copilot-cli/chronicle.md

@@ -9,6 +9,8 @@ contentType: concepts
 category:
   - Learn about Copilot # Copilot discovery page
   - Learn about Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/concepts/agents/copilot-cli/comparing-cli-features.md

@@ -9,6 +9,8 @@ contentType: concepts
 category:
   - Learn about Copilot # Copilot discovery page
   - Learn about Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/concepts/agents/copilot-cli/fleet.md

@@ -9,6 +9,8 @@ contentType: concepts
 category:
   - Learn about Copilot # Copilot discovery page
   - Learn about Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/concepts/agents/copilot-cli/index.md

@@ -15,4 +15,6 @@ children:
   - /research
   - /chronicle
 contentType: concepts
+docsTeamMetrics:
+  - copilot-cli
 ---

content/copilot/concepts/agents/copilot-cli/research.md

@@ -9,6 +9,8 @@ contentType: concepts
 category:
   - Learn about Copilot # Copilot discovery page
   - Learn about Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/administer-copilot-cli-for-your-enterprise.md

@@ -9,6 +9,8 @@ allowTitleToDifferFromFilename: true
 category:
   - Manage Copilot for a team # Copilot discovery page
   - Administer Copilot CLI # Copilot CLI bespoke landing page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Enabling or disabling {% data variables.copilot.copilot_cli_short %}

content/copilot/how-tos/copilot-cli/allowing-tools.md

@@ -8,6 +8,8 @@ contentType: how-tos
 category:
   - Author and optimize with Copilot # Copilot discovery page
   - Build with Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/automate-copilot-cli/automate-with-actions.md

@@ -11,6 +11,8 @@ category:
   - Author and optimize with Copilot
 redirect_from:
   - /copilot/how-tos/copilot-cli/automate-with-actions
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 You can run {% data variables.copilot.copilot_cli %} in a {% data variables.product.prodname_actions %} workflow to automate AI-powered tasks as part of your CI/CD process. For example, you can summarize recent repository activity, generate reports, or scaffold project content. {% data variables.copilot.copilot_cli %} runs on the Actions runner like any other CLI tool, so you can install it during a job and invoke it from workflow steps.

content/copilot/how-tos/copilot-cli/automate-copilot-cli/index.md

@@ -9,4 +9,6 @@ children:
   - /quickstart
   - /run-cli-programmatically
   - /automate-with-actions
+docsTeamMetrics:
+  - copilot-cli
 ---

content/copilot/how-tos/copilot-cli/automate-copilot-cli/quickstart.md

@@ -12,6 +12,8 @@ category:
   - Author and optimize with Copilot # Copilot discovery page
   - Build with Copilot CLI # Copilot CLI bespoke page
   - Quickstarts
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Overview

content/copilot/how-tos/copilot-cli/automate-copilot-cli/run-cli-programmatically.md

@@ -9,6 +9,8 @@ contentType: how-tos
 category:
   - Author and optimize with Copilot # Copilot discovery page
   - Build with Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/chronicle.md

@@ -9,6 +9,8 @@ contentType: how-tos
 category:
   - Author and optimize with Copilot # Copilot discovery page
   - Build with Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 {% data variables.copilot.copilot_cli_short %} stores the data from your CLI sessions locally on your machine. This session data allows you to:

content/copilot/how-tos/copilot-cli/cli-best-practices.md

@@ -10,6 +10,8 @@ category:
   - Build with Copilot CLI
   - Copilot in the CLI
   - Author and optimize with Copilot
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/cli-getting-started.md

@@ -11,6 +11,8 @@ category:
   - Build with Copilot CLI
   - Quickstarts
   - Author and optimize with Copilot
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/connecting-vs-code.md

@@ -9,6 +9,8 @@ contentType: how-tos
 category:
   - Author and optimize with Copilot # Copilot discovery page
   - Build with Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 Connecting {% data variables.copilot.copilot_cli_short %} to {% data variables.product.prodname_vscode_shortname %} gives you the best of both environments: the speed and flexibility of a terminal-based workflow, combined with the rich visual tools of your editor. With a connection established, you can:

content/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions.md

@@ -11,6 +11,8 @@ redirect_from:
   - /copilot/how-tos/copilot-cli/add-repository-instructions
   - /copilot/how-tos/copilot-cli/add-custom-instructions
 contentType: how-tos
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 {% data variables.product.prodname_copilot %} can provide responses that are tailored to your personal preferences, the way your team works, the tools you use, or the specifics of your project, if you provide it with enough context to do so. Instead of repeatedly adding this contextual detail to your prompts, you can create custom instructions that automatically add this information for you. The additional information is not displayed, but is available to {% data variables.product.prodname_copilot_short %} to allow it to generate higher quality responses.

content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md

@@ -9,6 +9,8 @@ contentType: how-tos
 category:
   - Configure Copilot CLI # Copilot CLI bespoke page
   - Author and optimize with Copilot # Copilot discovery page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 The Model Context Protocol (MCP) is an open standard that defines how applications share context with large language models (LLMs). You can connect MCP servers to {% data variables.copilot.copilot_cli %} to give {% data variables.product.prodname_copilot_short %} access to external tools, data sources, and services. For an overview of MCP, see [AUTOTITLE](/copilot/concepts/about-mcp).

content/copilot/how-tos/copilot-cli/customize-copilot/create-custom-agents-for-cli.md

@@ -10,6 +10,8 @@ category:
   - Author and optimize with Copilot # Copilot discovery page
   - Configure Copilot CLI # Copilot CLI bespoke page
 contentType: how-tos
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/customize-copilot/create-skills.md

@@ -10,6 +10,8 @@ category:
   - Configure Copilot # Copilot discovery page
   - Author and optimize with Copilot # Copilot discovery page
   - Configure Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 Agent skills are folders of instructions, scripts, and resources that {% data variables.product.prodname_copilot_short %} can load when relevant to improve its performance in specialized tasks. For more information, see [AUTOTITLE](/copilot/concepts/agents/about-agent-skills).

content/copilot/how-tos/copilot-cli/customize-copilot/index.md

@@ -16,4 +16,6 @@ children:
   - /plugins-finding-installing
   - /plugins-creating
   - /plugins-marketplace
+docsTeamMetrics:
+  - copilot-cli
 ---

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

@@ -11,6 +11,8 @@ category:
   - Configure Copilot CLI # Copilot CLI bespoke page
 redirect_from:
   - /copilot/how-tos/copilot-cli/customize-copilot/quickstart-for-customizing
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 You can download and install {% data variables.copilot.copilot_cli_short %}, and start using it straight away, without any additional configuration. However, you'll find that you can improve {% data variables.product.prodname_copilot_short %}'s responses if you spend a little time providing it with guidelines and context, and giving it access to tools that are relevant to your project. This article introduces the various ways in which you can customize {% data variables.copilot.copilot_cli_short %}.

content/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating.md

@@ -10,6 +10,8 @@ category:
   - Author and optimize with Copilot # Copilot discovery page
   - Configure Copilot CLI # Copilot CLI bespoke page
 contentType: how-tos
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing.md

@@ -10,6 +10,8 @@ category:
   - Author and optimize with Copilot # Copilot discovery page
   - Configure Copilot CLI # Copilot CLI bespoke page
 contentType: how-tos
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction

content/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace.md

@@ -10,6 +10,8 @@ category:
   - Author and optimize with Copilot # Copilot discovery page
   - Configure Copilot CLI # Copilot CLI bespoke page
 contentType: how-tos
+docsTeamMetrics:
+  - copilot-cli
 ---
 
 ## Introduction