diff --git a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
index f32e56b6ac90..d9bb976d0a92 100644
--- a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
+++ b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
@@ -482,18 +482,22 @@ Reviewers must have at least read access to the repository.
| `interval` | **Required.** Defines the frequency for {% data variables.product.prodname_dependabot %}. |
| `day` | Specify the day to run for a **weekly** interval. |
| `time` | Specify the time to run. |
+| `cronjob` | Defines the cron expression if the interval type is `cron`. |
| `timezone` | Specify the timezone of the `time` value. |
### `interval`
-Supported values: `daily`, `weekly`, or `monthly`
+Supported values: `daily`, `weekly`, `monthly`, `quarterly`, `semiannually`, `yearly`, 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 `quarterly` to run on the first day of each quarter (January, April, July, and October).
+* Use `semiannually` to run every six months, on the first day of January and July.
+* Use `yearly` to run on the first day of January.
+* Use `cron` for cron expression based scheduling option. See [`cronjob`](#cronjob).
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.
### `day`
@@ -508,6 +512,40 @@ Format: `hh:mm`
Optionally, run all updates for a package manager at a specific time of day. By default, times are interpreted as UTC.
+### `cronjob`
+
+Supported values: Valid cron expression in cron format or natural expression.
+
+Examples : `0 9 * * *`, `every day at 5pm`
+
+cron format is defined as the following:
+* `*` The minute field.
+* `*` The hour field (in 24-hour time).
+* `*` The day of the month (matches any day of the month).
+* `*` The month (matches any month).
+* `*` The day of the week (matches any day of the week).
+
+`0 9 * * *` is equivalent to "every day at 9am". `every day at 5pm` is equivalent to `0 17 * * *`.
+
+> [!NOTE]
+> A `cronjob` type schedule is required to use a `cron` interval.
+
+```yaml copy
+
+# Basic `dependabot.yml` file for cronjob
+
+version: 2
+updates:
+ # Enable version updates for npm
+ - package-ecosystem: "npm"
+ # Look for `package.json` and `lock` files in the `root` directory
+ directory: "/"
+ # Check the npm registry for updates based on `cronjob` value
+ schedule:
+ interval: "cron"
+ cronjob: "0 9 * * *"
+```
+
### `timezone`
Specify a time zone for the `time` value.
diff --git a/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md b/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md
index ff75f2a2e442..bcf9989d65b5 100644
--- a/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md
+++ b/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md
@@ -62,6 +62,8 @@ You're ready to start building real coding skills with {% data variables.product
Throughout your work on the project, engage in a long-running conversation with **{% data variables.product.prodname_copilot_chat_short %}**. Treat it as your **personal tutor**, asking questions as they arise and using it to navigate challenges or clarify concepts.
-> [!TIP] You can open {% data variables.product.prodname_copilot_chat_short %} with a keyboard shortcut: Ctrl+Alt+I (Windows/Linux) or Command+Shift+I (Mac).
+
+Open {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %} {% octicon "link-external" height:16 %}
+
{% data variables.product.prodname_copilot_chat_short %} is especially helpful for debugging your code. For step-by-step guidance, see [AUTOTITLE](/get-started/learning-to-code/learning-to-debug-with-github-copilot).
diff --git a/src/graphql/data/fpt/schema.docs.graphql b/src/graphql/data/fpt/schema.docs.graphql
index dbf1eaaea2d2..fa75d7e716c5 100644
--- a/src/graphql/data/fpt/schema.docs.graphql
+++ b/src/graphql/data/fpt/schema.docs.graphql
@@ -7899,7 +7899,7 @@ input CreateIssueInput {
"""
The Node ID of the issue type for this issue
"""
- issueTypeId: ID @possibleTypes(concreteTypes: ["IssueType"])
+ issueTypeId: ID
"""
An array of Node IDs of labels for this issue.
diff --git a/src/graphql/data/fpt/schema.json b/src/graphql/data/fpt/schema.json
index 22136ff992d6..1a08b234493f 100644
--- a/src/graphql/data/fpt/schema.json
+++ b/src/graphql/data/fpt/schema.json
@@ -100107,8 +100107,7 @@
"type": "ID",
"id": "id",
"kind": "scalars",
- "href": "/graphql/reference/scalars#id",
- "isDeprecated": false
+ "href": "/graphql/reference/scalars#id"
},
{
"name": "labelIds",
diff --git a/src/graphql/data/ghec/schema.docs.graphql b/src/graphql/data/ghec/schema.docs.graphql
index dbf1eaaea2d2..fa75d7e716c5 100644
--- a/src/graphql/data/ghec/schema.docs.graphql
+++ b/src/graphql/data/ghec/schema.docs.graphql
@@ -7899,7 +7899,7 @@ input CreateIssueInput {
"""
The Node ID of the issue type for this issue
"""
- issueTypeId: ID @possibleTypes(concreteTypes: ["IssueType"])
+ issueTypeId: ID
"""
An array of Node IDs of labels for this issue.
diff --git a/src/graphql/data/ghec/schema.json b/src/graphql/data/ghec/schema.json
index 22136ff992d6..1a08b234493f 100644
--- a/src/graphql/data/ghec/schema.json
+++ b/src/graphql/data/ghec/schema.json
@@ -100107,8 +100107,7 @@
"type": "ID",
"id": "id",
"kind": "scalars",
- "href": "/graphql/reference/scalars#id",
- "isDeprecated": false
+ "href": "/graphql/reference/scalars#id"
},
{
"name": "labelIds",