Repo sync

content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-dependabot-alerts.md

@@ -24,12 +24,12 @@ This article explains how to access and view these metrics for your organization
 {% data reusables.organizations.security-overview %}
 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 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 %}.
 
 ## Configuring funnel categories
 
-The default funnel order is `has:patch, severity:critical,high, epss_percentage>=0.01`. By tailoring the funnel’s order, you and your teams can focus on the vulnerabilities that matter most to your organization, environments, or regulatory obligations, making remediation efforts more effective and aligned with your specific needs.
+The default funnel order is `has:patch, severity:critical,high, epss-percentage:>=0.01`. By tailoring the funnel’s order, you and your teams can focus on the vulnerabilities that matter most to your organization, environments, or regulatory obligations, making remediation efforts more effective and aligned with your specific needs.
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.security-overview %}

content/code-security/reference/security-at-scale/overview-dashboard-filters.md

@@ -191,7 +191,7 @@ For more information about production context, see [AUTOTITLE](/code-security/tu
 | `assignee` | Display alerts by assignee username or team, for example: `assignee:@octocat`, `assignee:@copilot`, or `assignee:@github/security-team`.|
 |{% endif %}|
 |`ecosystem`|Display {% data variables.product.prodname_dependabot_alerts %} detected in a specified ecosystem, for example: `ecosystem:Maven`.|
-|`epss_percentage`|Display {% data variables.product.prodname_dependabot_alerts %} whose EPSS score meets the defined criteria, for example: `epss_percentage:>=0.01`|
+|`epss-percentage`|Display {% data variables.product.prodname_dependabot_alerts %} whose EPSS score meets the defined criteria, for example: `epss-percentage:>=0.01`|
 |`has`|Display {% data variables.product.prodname_dependabot_alerts %} for vulnerabilities where either a secure version is already available (`patch`) or where at least one call from the repository to a vulnerable function is detected (`vulnerable-calls`). For more information, see [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/view-dependabot-alerts).|
 |`is`|Display {% data variables.product.prodname_dependabot_alerts %} that are open (`open`) or closed (`closed`).|
 |`package`|Display {% data variables.product.prodname_dependabot_alerts %} detected in the specified package, for example: `package:semver`.|

content/code-security/tutorials/manage-security-alerts/prioritizing-dependabot-alerts-using-metrics.md

@@ -49,7 +49,7 @@ Start by identifying alerts with the highest severity by using the `severity-cri
 
 ### 3. Assess exploitability and reachability
 
-Prioritize vulnerabilities that are the most likely to be exploited in your codebase. To identify alerts that are most likely to be exploited, you can use the `epss_percentage` filter associated to a value (for example `epss_percentage>=0.10`).
+Prioritize vulnerabilities that are the most likely to be exploited in your codebase. To identify alerts that are most likely to be exploited, you can use the `epss-percentage` filter associated to a value (for example `epss-percentage:>=0.10`).
 
 ### 4. Review dependency scope and relationship
 

data/reusables/security-overview/filter-dependabot-metrics.md

@@ -12,5 +12,5 @@
 |`package`|Display {% data variables.product.prodname_dependabot_alerts %} detected in the specified package, for example: `package:lodash`.|
 |`ecosystem`|Display {% data variables.product.prodname_dependabot_alerts %} detected in a specified ecosystem, for example: `ecosystem:Maven`.|
 |`relationship`|Display {% data variables.product.prodname_dependabot_alerts %} of the specified relationship, for example: `relationship:indirect`.|
-|`epss_percentage`|Display {% data variables.product.prodname_dependabot_alerts %} whose EPSS score meets the defined criteria, for example: `epss_percentage:>=0.01`|
+|`epss-percentage`|Display {% data variables.product.prodname_dependabot_alerts %} whose EPSS score meets the defined criteria, for example: `epss-percentage:>=0.01`|
 |`exclude <QUALIFIER>`|Applies to all the available qualifiers.</br>Display alerts that do not match the selected qualifier from the list of {% data variables.product.prodname_dependabot_alerts %}|

src/graphql/data/fpt/category-map.json

@@ -1307,6 +1307,7 @@
     "pullrequestreviewdecision": "pulls",
     "pullrequestreviewevent": "pulls",
     "pullrequestreviewstate": "pulls",
+    "pullrequestreviewthreadresolutionreason": "pulls",
     "pullrequestreviewthreadsubjecttype": "pulls",
     "pullrequeststate": "pulls",
     "pullrequesttimelineitemsitemtype": "pulls",

src/graphql/data/fpt/changelog.json

@@ -1,4 +1,21 @@
 [
+  {
+    "schemaChanges": [
+      {
+        "title": "The GraphQL schema includes these changes:",
+        "changes": [
+          "<p>Type <code>PullRequestReviewThreadResolutionReason</code> was added</p>",
+          "<p>Enum value <code>ADDRESSED</code> was added to enum <code>PullRequestReviewThreadResolutionReason</code></p>",
+          "<p>Enum value <code>INVALID</code> was added to enum <code>PullRequestReviewThreadResolutionReason</code></p>",
+          "<p>Enum value 'WONT_FIX<code>was added to enum</code>PullRequestReviewThreadResolutionReason'</p>",
+          "<p>Input field <code>resolutionReason</code> of type <code>PullRequestReviewThreadResolutionReason</code> was added to input object type <code>ResolveReviewThreadInput</code></p>"
+        ]
+      }
+    ],
+    "previewChanges": [],
+    "upcomingChanges": [],
+    "date": "2026-08-25"
+  },
   {
     "schemaChanges": [
       {

src/graphql/data/fpt/schema-issues.json

@@ -11566,8 +11566,7 @@
           "description": "<p>The ID of the organization where the issue field will be created.</p>",
           "type": "ID!",
           "id": "id",
-          "href": "/graphql/reference/other#scalar-id",
-          "isDeprecated": false
+          "href": "/graphql/reference/other#scalar-id"
         },
         {
           "name": "visibility",

src/graphql/data/fpt/schema-pulls.json

@@ -8319,6 +8319,28 @@
       ],
       "category": "pulls"
     },
+    {
+      "name": "PullRequestReviewThreadResolutionReason",
+      "id": "pullrequestreviewthreadresolutionreason",
+      "href": "/graphql/reference/pulls#enum-pullrequestreviewthreadresolutionreason",
+      "description": "<p>The possible reasons a pull request review thread was resolved.</p>",
+      "isDeprecated": false,
+      "values": [
+        {
+          "name": "ADDRESSED",
+          "description": "<p>The review comment was addressed.</p>"
+        },
+        {
+          "name": "INVALID",
+          "description": "<p>The review comment is invalid.</p>"
+        },
+        {
+          "name": "WONT_FIX",
+          "description": "<p>The review comment will not be addressed.</p>"
+        }
+      ],
+      "category": "pulls"
+    },
     {
       "name": "PullRequestReviewThreadSubjectType",
       "id": "pullrequestreviewthreadsubjecttype",
@@ -10570,6 +10592,13 @@
           "id": "string",
           "href": "/graphql/reference/other#scalar-string"
         },
+        {
+          "name": "resolutionReason",
+          "description": "<p>The reason a Copilot code review thread was resolved.</p>",
+          "type": "PullRequestReviewThreadResolutionReason",
+          "id": "pullrequestreviewthreadresolutionreason",
+          "href": "/graphql/reference/pulls#enum-pullrequestreviewthreadresolutionreason"
+        },
         {
           "name": "threadId",
           "description": "<p>The ID of the thread to resolve.</p>",

src/graphql/data/fpt/schema.docs.graphql

@@ -8453,7 +8453,7 @@ input CreateIssueFieldInput {
   """
   The ID of the organization where the issue field will be created.
   """
-  ownerId: ID! @possibleTypes(concreteTypes: ["Organization"])
+  ownerId: ID!
 
   """
   The visibility of the issue field.
@@ -46858,6 +46858,26 @@ type PullRequestReviewThreadEdge {
   node: PullRequestReviewThread
 }
 
+"""
+The possible reasons a pull request review thread was resolved.
+"""
+enum PullRequestReviewThreadResolutionReason @docsCategory(name: "pulls") {
+  """
+  The review comment was addressed.
+  """
+  ADDRESSED
+
+  """
+  The review comment is invalid.
+  """
+  INVALID
+
+  """
+  The review comment will not be addressed.
+  """
+  WONT_FIX
+}
+
 """
 The possible subject types of a pull request review comment.
 """
@@ -59316,6 +59336,11 @@ input ResolveReviewThreadInput {
   """
   clientMutationId: String
 
+  """
+  The reason a Copilot code review thread was resolved.
+  """
+  resolutionReason: PullRequestReviewThreadResolutionReason
+
   """
   The ID of the thread to resolve
   """

src/graphql/data/ghec/category-map.json

@@ -1307,6 +1307,7 @@
     "pullrequestreviewdecision": "pulls",
     "pullrequestreviewevent": "pulls",
     "pullrequestreviewstate": "pulls",
+    "pullrequestreviewthreadresolutionreason": "pulls",
     "pullrequestreviewthreadsubjecttype": "pulls",
     "pullrequeststate": "pulls",
     "pullrequesttimelineitemsitemtype": "pulls",

src/graphql/data/ghec/schema-issues.json

@@ -11566,8 +11566,7 @@
           "description": "<p>The ID of the organization where the issue field will be created.</p>",
           "type": "ID!",
           "id": "id",
-          "href": "/graphql/reference/other#scalar-id",
-          "isDeprecated": false
+          "href": "/graphql/reference/other#scalar-id"
         },
         {
           "name": "visibility",

src/graphql/data/ghec/schema-pulls.json

@@ -8319,6 +8319,28 @@
       ],
       "category": "pulls"
     },
+    {
+      "name": "PullRequestReviewThreadResolutionReason",
+      "id": "pullrequestreviewthreadresolutionreason",
+      "href": "/graphql/reference/pulls#enum-pullrequestreviewthreadresolutionreason",
+      "description": "<p>The possible reasons a pull request review thread was resolved.</p>",
+      "isDeprecated": false,
+      "values": [
+        {
+          "name": "ADDRESSED",
+          "description": "<p>The review comment was addressed.</p>"
+        },
+        {
+          "name": "INVALID",
+          "description": "<p>The review comment is invalid.</p>"
+        },
+        {
+          "name": "WONT_FIX",
+          "description": "<p>The review comment will not be addressed.</p>"
+        }
+      ],
+      "category": "pulls"
+    },
     {
       "name": "PullRequestReviewThreadSubjectType",
       "id": "pullrequestreviewthreadsubjecttype",
@@ -10570,6 +10592,13 @@
           "id": "string",
           "href": "/graphql/reference/other#scalar-string"
         },
+        {
+          "name": "resolutionReason",
+          "description": "<p>The reason a Copilot code review thread was resolved.</p>",
+          "type": "PullRequestReviewThreadResolutionReason",
+          "id": "pullrequestreviewthreadresolutionreason",
+          "href": "/graphql/reference/pulls#enum-pullrequestreviewthreadresolutionreason"
+        },
         {
           "name": "threadId",
           "description": "<p>The ID of the thread to resolve.</p>",

src/graphql/data/ghec/schema.docs.graphql

@@ -8453,7 +8453,7 @@ input CreateIssueFieldInput {
   """
   The ID of the organization where the issue field will be created.
   """
-  ownerId: ID! @possibleTypes(concreteTypes: ["Organization"])
+  ownerId: ID!
 
   """
   The visibility of the issue field.
@@ -46858,6 +46858,26 @@ type PullRequestReviewThreadEdge {
   node: PullRequestReviewThread
 }
 
+"""
+The possible reasons a pull request review thread was resolved.
+"""
+enum PullRequestReviewThreadResolutionReason @docsCategory(name: "pulls") {
+  """
+  The review comment was addressed.
+  """
+  ADDRESSED
+
+  """
+  The review comment is invalid.
+  """
+  INVALID
+
+  """
+  The review comment will not be addressed.
+  """
+  WONT_FIX
+}
+
 """
 The possible subject types of a pull request review comment.
 """
@@ -59316,6 +59336,11 @@ input ResolveReviewThreadInput {
   """
   clientMutationId: String
 
+  """
+  The reason a Copilot code review thread was resolved.
+  """
+  resolutionReason: PullRequestReviewThreadResolutionReason
+
   """
   The ID of the thread to resolve
   """

src/languages/lib/correct-translation-content.ts

@@ -891,6 +891,12 @@ export function correctTranslatedContentStrings(
     // `{% 行标题结束 %}` — order swap (rowheaders + end)
     content = content.replaceAll('{% 行标题结束 %}', '{% endrowheaders %}')
     content = content.replaceAll('{%- 行标题结束 %}', '{%- endrowheaders %}')
+    // `{% 结束表头列 %}` — "end table header column" = endrowheaders. Found in
+    // codeql-query-tables reusables (python/rust/java/go/ruby/javascript), where
+    // the opener `{% rowheaders %}` was correctly left in English but the closer
+    // was translated, leaving the tag unclosed and breaking table rendering.
+    content = content.replaceAll('{% 结束表头列 %}', '{% endrowheaders %}')
+    content = content.replaceAll('{%- 结束表头列 %}', '{%- endrowheaders %}')
     // Capitalized `{% Variables.X %}` / `{% Reusables.X %}` — translator title-cased
     content = content.replaceAll('{% data Variables.', '{% data variables.')
     content = content.replaceAll('{% data Reusables.', '{% data reusables.')

src/languages/tests/correct-translation-content.ts

@@ -624,6 +624,12 @@ describe('correctTranslatedContentStrings', () => {
       expect(fix('{%- 行标题 %}', 'zh')).toBe('{%- rowheaders %}')
     })
 
+    test('fixes 结束表头列 → endrowheaders', () => {
+      expect(fix('{% 结束表头列 %}', 'zh')).toBe('{% endrowheaders %}')
+      expect(fix('{%- 结束表头列 %}', 'zh')).toBe('{%- endrowheaders %}')
+      expect(fix('{% endrowheaders %}', 'zh')).toBe('{% endrowheaders %}')
+    })
+
     test('fixes 数据变量 → data variables', () => {
       expect(fix('{% 数据变量.product.github %}', 'zh')).toBe('{% data variables.product.github %}')
     })