Merge pull request #40800 from github/repo-sync

Repo sync

Author: docs-bot

.github/actions/get-changed-files/action.yml

@@ -33,6 +33,7 @@ runs:
     - name: Gather changed files
       id: get_changes
       env:
+        INPUT_FILES: ${{ inputs.files }}
         INPUT_HEAD: ${{ inputs.head || github.event.pull_request.head.ref || github.event.merge_group.head_ref ||  github.ref_name }}
         INPUT_OUTPUT_FILE: ${{ inputs.output_file }}
       shell: bash

assets/images/banner-images/hero-2.png

@@ -53,6 +53,7 @@ This table lists the secrets supported by {% data variables.product.prodname_sec
 
 | Provider | Token |
 |----------|:--------------------|
+|  Generic | ec_private_key |
 |  Generic | http_basic_authentication_header |
 |  Generic | http_bearer_authentication_header |
 |  Generic | mongodb_connection_string |

assets/images/banner-images/hero-3.png

@@ -151,16 +151,34 @@ A CTA is an explicit direction to the user to take an immediate action, such as
 
 For example, the CTA on [AUTOTITLE](/enterprise-cloud@latest/admin/overview/setting-up-a-trial-of-github-enterprise-cloud) links to [an enterprise sales page](https://github.com/account/enterprises/new?ref_product=ghec&ref_type=trial&ref_style=text&ref_plan=enterprise) on {% data variables.product.prodname_dotcom_the_website %}.
 
-Style a CTA using the following format.
+### Required CTA parameters
+
+* `ref_product`:
+  * **Purpose**: The GitHub product the CTA leads users to.
+  * **Allowed values**: `copilot`, `ghec`, `desktop`
+  * **Example**: `ref_product=copilot`
+* `ref_type`:
+  * **Purpose**: The type of action the CTA encourages users to take.
+  * **Allowed values**: `trial`, `purchase`, `engagement`
+  * **Example**: `ref_type=purchase`
+* `ref_style`:
+  * **Purpose**: The way we are formatting the CTA in the docs.
+  * **Allowed values**: `button` or `text`
+  * **Example**: `ref_style=button`
+* `ref_plan` (_optional_):
+  * **Purpose**: For links to sign up for or trial a plan, the specific plan we link to.
+  * **Allowed values**: `enterprise`, `business`, `pro`, `free`
+  * **Example**: `ref_plan=business`
+
+Replace the placeholders with the relevant information for your CTA, where `DESTINATION/URL` is the URL that the button should navigate to:
 
 ```html
-{% raw %}<a href="https://github.com/DESTINATION/URL?ref_cta=CTA+NAME&ref_loc=LOCATION&ref_page=docs" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Try PRODUCT NAME</span> {% octicon "link-external" height:16 %}</a>{% endraw %}
+{% raw %}<a href="https://github.com/DESTINATION/URL?ref_product=PRODUCT&ref_type=TYPE&ref_style=STYLE&ref_plan=PLAN" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Try PRODUCT NAME</span> {% octicon "link-external" height:16 %}</a>{% endraw %}
 ```
 
-Replace the placeholders with the relevant information for your CTA.
-* `DESTINATION/URL`: The URL that the button should navigate to.
-* `CTA+NAME`: The name of the CTA. For example, `GHEC+trial` or `Copilot+Business+Trial`.
-* `LOCATION`: The location in {% data variables.product.prodname_docs %} of the CTA. For example, `Setting+up+a+trial+of+GitHub+Enterprise+Cloud`.
+### Getting help with CTAs
+
+For help building a valid CTA URL, you can enter the command `npm run cta-builder` in your docs repo checkout. Answer each question and at the end you'll see your valid CTA.
 
 ## Code
 

assets/images/banner-images/hero-4.png

@@ -72,6 +72,7 @@
 | GHD054 | third-party-actions-reusable | Code examples with third-party actions must include disclaimer reusable | warning | actions, reusable, third-party |
 | GHD055 | frontmatter-validation | Frontmatter properties must meet character limits and required property requirements | warning | frontmatter, character-limits, required-properties |
 | GHD056 | frontmatter-landing-recommended | Only landing pages can have recommended articles, there should be no duplicate recommended articles, and all recommended articles must exist | error | frontmatter, landing, recommended |
+| GHD057 | ctas-schema | CTA URLs must conform to the schema | error | ctas, schema, urls |
 | [search-replace](https://github.com/OnkarRuikar/markdownlint-rule-search-replace) | deprecated liquid syntax: octicon-<icon-name> | The octicon liquid syntax used is deprecated. Use this format instead `octicon "<octicon-name>" aria-label="<Octicon aria label>"` | error |  |
 | [search-replace](https://github.com/OnkarRuikar/markdownlint-rule-search-replace) | deprecated liquid syntax: site.data | Catch occurrences of deprecated liquid data syntax. | error |  |
 | [search-replace](https://github.com/OnkarRuikar/markdownlint-rule-search-replace) | developer-domain | Catch occurrences of developer.github.com domain. | error |  |

assets/images/banner-images/hero-5.png

@@ -1,4 +1,4 @@
-# Data-driven tables
+# YAML-powered tables
 
 ## Overview
 
@@ -34,7 +34,7 @@ Every data-driven table needs **three files** that work together:
 |-----------|----------|---------|
 | **Data file** | `data/tables/` | Stores the table content in YAML format |
 | **Content file** | `content/` | Displays the table using Liquid templating |
-| **Schema file** | `src/data-directory/lib/data-schemas/` | Validates the YAML structure |
+| **Schema file** | `src/data-directory/lib/data-schemas/tables/` | Validates the YAML structure |
 
 **Estimated time**: 30-60 minutes for a new table
 
@@ -49,7 +49,7 @@ Create a new `.yml` file in `data/tables/` with a descriptive name.
 Create a YAML structure that will allow me to generate a table that looks like: 
 [describe your table headers, rows, and columns OR attach an example]
 
-See src/secret-scanning/data/public-docs.yml for an example.
+See data/tables/supported-code-languages.yml for an example.
 ```
 
 ### Step 2: Create the content display
@@ -62,22 +62,22 @@ Create a Markdown table that is dynamically rendered using Liquid code.
 Pull data from data/tables/TABLE_NAME.yml. 
 The table should look like: [describe your desired output OR attach an example]
 
-See content/code-security/secret-scanning/introduction/supported-secret-scanning-patterns.md for an example.
+See content/get-started/learning-about-github/github-language-support.md for an example.
 Liquid docs: https://shopify.github.io/liquid
 ```
 
 **💡 Tip**: Iterate between Steps 1 and 2 until the table renders correctly.
 
 ### Step 3: Create the schema file
 
-Create a `.ts` file in `src/data-directory/lib/data-schemas/` with the same name as your YAML file.
+Create a `.ts` file in `src/data-directory/lib/data-schemas/tables/` with the same name as your YAML file.
 
 **Copilot prompt template:**
 ```
 Create a TypeScript schema following prior art under data-schemas that enforces 
 the structure of the data/TABLE_NAME.yml file.
 
-See src/data-directory/lib/data-schemas/learning-tracks.ts for an example.
+See src/data-directory/lib/data-schemas/tables/supported-code-languages.ts for an example.
 ```
 
 ## Testing and validation