Repo sync

content/copilot/how-tos/configure-custom-instructions/add-repository-instructions.md

@@ -249,11 +249,11 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Repository-wide custom instructions**, which apply to all requests made in the context of a repository.
 
-  These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions).
+  These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions-1).
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
+  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-1).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 
@@ -303,11 +303,11 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Repository-wide custom instructions** apply to all requests made in the context of a repository.
 
-  These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions-1).
+  These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions-2).
 
 * **Path-specific custom instructions** apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-1).
+  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 

data/reusables/contributing/content-linter-rules.md

@@ -57,7 +57,6 @@
 | GHD046 | outdated-release-phase-terminology | Outdated release phase terminology should be replaced with current GitHub terminology | warning | terminology, consistency, release-phases |
 | GHD047 | table-column-integrity | Tables must have consistent column counts across all rows | warning | tables, accessibility, formatting |
 | GHD051 | frontmatter-versions-whitespace | Versions frontmatter should not contain unnecessary whitespace | warning | frontmatter, versions |
-| GHD053 | header-content-requirement | Headers must have content between them, such as an introduction | warning | headers, structure, content |
 | GHD054 | third-party-actions-reusable | Code examples with third-party actions must include disclaimer reusable | warning | actions, reusable, third-party |
 | 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 |

src/content-linter/lib/linting-rules/index.ts

@@ -46,7 +46,6 @@ import { octiconAriaLabels } from '@/content-linter/lib/linting-rules/octicon-ar
 import { liquidIfversionVersions } from '@/content-linter/lib/linting-rules/liquid-ifversion-versions'
 import { outdatedReleasePhaseTerminology } from '@/content-linter/lib/linting-rules/outdated-release-phase-terminology'
 import { frontmatterVersionsWhitespace } from '@/content-linter/lib/linting-rules/frontmatter-versions-whitespace'
-import { headerContentRequirement } from '@/content-linter/lib/linting-rules/header-content-requirement'
 import { thirdPartyActionsReusable } from '@/content-linter/lib/linting-rules/third-party-actions-reusable'
 import { frontmatterLandingRecommended } from '@/content-linter/lib/linting-rules/frontmatter-landing-recommended'
 import { ctasSchema } from '@/content-linter/lib/linting-rules/ctas-schema'
@@ -111,7 +110,6 @@ export const gitHubDocsMarkdownlint = {
     outdatedReleasePhaseTerminology, // GHD046
     tableColumnIntegrity, // GHD047
     frontmatterVersionsWhitespace, // GHD051
-    headerContentRequirement, // GHD053
     thirdPartyActionsReusable, // GHD054
     frontmatterLandingRecommended, // GHD056
     ctasSchema, // GHD057

src/content-linter/scripts/lint-content.ts

@@ -738,7 +738,7 @@ function getCustomRule(ruleName: string): Rule | MarkdownlintRule {
 }
 
 // Check if a rule should be included based on user-specified rules
-// Handles both short names (e.g., GHD053, MD001) and long names (e.g., header-content-requirement, heading-increment)
+// Handles both short names (e.g., GHD047, MD001) and long names (e.g., table-column-integrity, heading-increment)
 export function shouldIncludeRule(ruleName: string, runRules: string[]) {
   // First check if the rule name itself is in the list
   if (runRules.includes(ruleName)) {

src/content-linter/style/github-docs.ts

@@ -186,12 +186,6 @@ const githubDocsConfig = {
     'partial-markdown-files': true,
     'yml-files': true,
   },
-  'header-content-requirement': {
-    // GHD053
-    severity: 'warning',
-    'partial-markdown-files': true,
-    'yml-files': true,
-  },
   'third-party-actions-reusable': {
     // GHD054
     severity: 'warning',