Repo sync

content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-mandatory-two-factor-authentication.md

@@ -24,9 +24,6 @@ Your account is selected for mandatory 2FA if you have taken some action on {% d
 
 {% data variables.product.prodname_dotcom %} is continually assessing improvements to our account security features and 2FA requirements, so these criteria may change over time.
 
-> [!NOTE]
-> If your account has an education coupon active, it is exempt from mandatory 2FA.
-
 ### About mandatory 2FA for organizations and enterprises
 
 Mandatory 2FA is required by {% data variables.product.prodname_dotcom %} itself to improve security for both individual developers and the broader software development ecosystem. Your administrator may also require 2FA enablement as a requirement to join their organization or enterprise, but those requirements are separate from this program. To find which users have enabled 2FA or are required to do so, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-whether-members-in-your-enterprise-have-2fa-enabled) or [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled).

content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md

@@ -610,6 +610,8 @@ Reviewers must have at least read access to the repository.
 | `cronjob` | Defines the cron expression if the interval type is `cron`. |
 | `timezone` | Specify the timezone of the `time` value.  |
 
+{% ifversion fpt or ghec %}
+
 ### `interval`
 
 Supported values: `daily`, `weekly`, `monthly`, `quarterly`, `semiannually`, `yearly`, or `cron`
@@ -624,6 +626,21 @@ Each package manager **must** define a schedule interval.
 * Use `yearly` to run on the first day of January.
 * Use `cron` for cron expression based scheduling option. See [`cronjob`](#cronjob).
 
+{% elsif ghes %}
+
+### `interval`
+
+Supported values: `daily`, `weekly`, `monthly`, or `cron`
+
+Each package manager **must** define a schedule interval.
+
+* Use `daily` to run on every weekday, Monday to Friday.
+* Use `weekly` to run once a week, by default on Monday.
+* Use `monthly` to run on the first day of each month.
+* Use `cron` for cron expression based scheduling option. See [`cronjob`](#cronjob).
+
+{% endif %}
+
 By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. You can use the `time` and `timezone` parameters to set a specific runtime for all intervals.  If you use a `cron` interval, you can define the update time with a `cronjob` expression.
 
 ### `day`

content/copilot/reference/policy-conflicts.md

@@ -53,6 +53,7 @@ Feature, model, and privacy settings for users are set according to the **least
 | Editor preview features | Least restrictive organization | [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-pre-release-license-terms) |
 | {% data variables.product.prodname_github_models %}, one policy per model | Least restrictive organization | [AUTOTITLE](/github-models/github-models-at-scale/manage-models-at-scale) |
 | MCP servers in {% data variables.product.prodname_copilot_short %} | Least restrictive organization | [AUTOTITLE](/copilot/using-github-copilot/coding-agent/extending-copilot-coding-agent-with-mcp) |
+| {% data variables.product.prodname_copilot_short %}-generated commit messages | Least restrictive organization | [AUTOTITLE](/copilot/responsible-use/copilot-commit-message-generation) |
 
 ## Next steps
 

package.json

@@ -252,7 +252,7 @@
     "@graphql-inspector/core": "^6.1.0",
     "@graphql-tools/load": "^8.0.19",
     "@octokit/rest": "22.0.0",
-    "@playwright/test": "^1.50",
+    "@playwright/test": "^1.56",
     "@types/accept-language-parser": "1.5.7",
     "@types/cheerio": "^0.22.35",
     "@types/connect-timeout": "1.9.0",

src/landings/components/journey/JourneyLearningTracks.module.css

@@ -78,7 +78,7 @@
 
 /* Hide only the timeline line that extends below the last badge, preserve everything else */
 .timelineContainer :global(.Timeline-Item:last-child::before) {
-  background: linear-gradient(to bottom, var(--borderColor-default, #d1d9e0) 0%, var(--borderColor-default, #d1d9e0) 30%, transparent 30%, transparent 100%) !important;
+  background: linear-gradient(to bottom, var(--borderColor-muted, var(--color-border-muted)) 0%, var(--borderColor-muted, var(--color-border-muted)) 30%, transparent 30%, transparent 100%) !important;
 }
 
 .timelineBadge {