Merge branch 'github:main' into main

Author: haaami01

.babelrc

@@ -2,51 +2,67 @@
 // https://github.com/microsoft/vscode-dev-containers/tree/v0.177.0/containers/javascript-node
 // -
 {
-	"name": "docs.github.com",
-	"build": {
-		"dockerfile": "Dockerfile",
-		// Update 'VARIANT' to pick a Node version
-		"args": { "VARIANT": "18" }
-	},
-
-	// Set *default* container specific settings.json values on container create.
-	"settings": {
-		"terminal.integrated.shell.linux": "/bin/bash",
-		"cSpell.language": ",en"
-	},
-
-	// Install features. Type 'feature' in the VS Code command palette for a full list.
-	"features": {
-		"sshd": "latest"
-	 },
-
-	// Visual Studio Code extensions which help authoring for docs.github.com.
-	"extensions": [
-		"dbaeumer.vscode-eslint",
-		"sissel.shopify-liquid",
-		"davidanson.vscode-markdownlint",
-		"bierner.markdown-preview-github-styles",
-		"streetsidesoftware.code-spell-checker",
-		"alistairchristie.open-reusables"
-	],
-
-	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-	"forwardPorts": [4000],
-		
-	"portsAttributes": {
-		"4000": {
-        		"label": "Preview",
-        		"onAutoForward": "openPreview"
-      		}
-	},
-
-	// Use 'postCreateCommand' to run commands after the container is created.
-	"postCreateCommand": "npm ci",
-
-	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
-	"remoteUser": "node"
-,
-	"hostRequirements": {
-		"memory": "8gb"
-	 }
+    "name": "docs.github.com",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version
+        "args": { "VARIANT": "18" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "cSpell.language": ",en"
+    },
+
+    // Install features. Type 'feature' in the VS Code command palette for a full list.
+    "features": {
+        "sshd": "latest"
+    },
+
+    "customizations": {
+        "vscode": {
+            "settings": {},
+            // Visual Studio Code extensions which help authoring for docs.github.com.
+            "extensions": [
+                "dbaeumer.vscode-eslint",
+                "sissel.shopify-liquid",
+                "davidanson.vscode-markdownlint",
+                "bierner.markdown-preview-github-styles",
+                "streetsidesoftware.code-spell-checker",
+                "alistairchristie.open-reusables",
+                "GitHub.copilot",
+                "GitHub.copilot-chat"
+            ]
+        },
+        "codespaces": {
+            "repositories": {
+                // allow Codespaces to pull from separate repo when user has access
+                "github/docs-early-access": {
+                    "permissions": {
+                        "contents": "write"
+                    }
+                }
+            }
+        }
+    },
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    "forwardPorts": [4000],
+
+    "portsAttributes": {
+        "4000": {
+            "label": "Preview"
+        }
+    },
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    "postCreateCommand": "npm ci",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node",
+
+    "hostRequirements": {
+        "memory": "8gb"
+    }
 }

.devcontainer/devcontainer.json

@@ -5,7 +5,6 @@
 contributing/
 docs/
 node_modules/
-script/
 tests/
 # Folder is cloned during the preview + prod workflows, the assets are merged into other locations for use before the build
 docs-early-access/

.dockerignore

@@ -3,26 +3,15 @@
 # https://docs.github.com/articles/about-codeowners
 # https://git-scm.com/docs/gitignore
 
-# Engineering
-*.js @github/docs-engineering
-*.ts @github/docs-engineering
-*.tsx @github/docs-engineering
-/.github/ @github/docs-engineering
-/script/ @github/docs-engineering
-/includes/ @github/docs-engineering
-Dockerfile @github/docs-engineering
-package-lock.json @github/docs-engineering
-package.json @github/docs-engineering
-
 # Site Policy
 /content/site-policy/ @github/site-policy-admins
 
-# Content strategy
-/contributing/content-markup-reference.md @github/docs-content-strategy
-/contributing/content-style-guide.md @github/docs-content-strategy
-/contributing/content-model.md @github/docs-content-strategy
-/contributing/content-style-guide.md @github/docs-content-strategy
-/contributing/content-templates.md @github/docs-content-strategy
+# Enterprise
+/data/release-notes/**/*.yml @github/docs-content-enterprise
+src/ghes-releases/lib/enterprise-dates.json @github/docs-content-enterprise
 
 # Requires review of #actions-oidc-integration, docs-engineering/issues/1506
 content/actions/deployment/security-hardening-your-deployments/** @github/oidc
+
+# RAI - CELA
+data/reusables/rai/** @github/legal-product

.eslintrc.cjs

@@ -10,7 +10,7 @@ Use the table of contents icon <img src="/contributing/images/table-of-contents.
 
 ## New contributor guide
 
-To get an overview of the project, read the [README](README.md). Here are some resources to help you get started with open source contributions:
+To get an overview of the project, read the [README](README.md) file. Here are some resources to help you get started with open source contributions:
 
 - [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
 - [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git)
@@ -20,7 +20,7 @@ To get an overview of the project, read the [README](README.md). Here are some r
 
 ## Getting started
 
-To navigate our codebase with confidence, see [the introduction to working in the docs repository](/contributing/working-in-docs-repository.md) :confetti_ball:. For more information on how we write our markdown files, see [the GitHub Markdown reference](contributing/content-markup-reference.md).
+To navigate our codebase with confidence, see [the introduction to working in the docs repository](/contributing/README.md) :confetti_ball:. For more information on how we write our markdown files, see "[Using Makrdown and Liquid in GitHub Docs](https://docs.github.com/en/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs).
 
 Check to see what [types of contributions](/contributing/types-of-contributions.md) we accept before making changes. Some of them don't even require writing a single line of code :sparkles:.
 
@@ -32,7 +32,7 @@ If you spot a problem with the docs, [search if an issue already exists](https:/
 
 #### Solve an issue
 
-Scan through our [existing issues](https://github.com/github/docs/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See [Labels](/contributing/how-to-use-labels.md) for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
+Scan through our [existing issues](https://github.com/github/docs/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See "[Label reference](https://docs.github.com/en/contributing/collaborating-on-github-docs/label-reference)" for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
 
 ### Make Changes
 
@@ -62,7 +62,7 @@ For more information about using a codespace for working on GitHub documentation
 
 ### Commit your update
 
-Commit the changes once you are happy with them. Don't forget to [self-review](/contributing/self-review.md) to speed up the review process:zap:.
+Commit the changes once you are happy with them. Don't forget to use the "[Self review checklist](https://docs.github.com/en/contributing/collaborating-on-github-docs/self-review-checklist) to speed up the review process :zap:.
 
 ### Pull Request
 

.github/CODEOWNERS

@@ -9,7 +9,7 @@ body:
         **HUBBERS!!** This is the github/docs open source repo. You may want to open an issue in the internal-only github/docs-content repo instead.
 
         * For questions, ask in [Discussions](https://github.com/github/docs/discussions).
-        * Before you file an issue read the [Contributing guide](https://github.com/github/docs/blob/main/CONTRIBUTING.md).
+        * Before you file an issue read the [Contributing guide](https://docs.github.com/en/contributing).
         * Check to make sure someone hasn't already opened a similar [issue](https://github.com/github/docs/issues).
 
   - type: checkboxes
@@ -18,7 +18,7 @@ body:
       label: Code of Conduct
       description: This project has a Code of Conduct that all participants are expected to understand and follow.
       options:
-        - label: I have read and agree to the GitHub Docs project's [Code of Conduct](https://github.com/github/docs/blob/main/CODE_OF_CONDUCT.md)
+        - label: I have read and agree to the GitHub Docs project's [Code of Conduct](https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md)
           required: true
 
   - type: textarea
@@ -34,13 +34,15 @@ body:
       description: |
         - Give as much detail as you can to help us understand the change you want to see. 
         - Why should the docs be changed? What use cases does it support? 
-        - What is the expected outcome?
+        - What is the expected outcome or behavior?
     validations:
       required: true
 
   - type: textarea
     attributes:
       label: Additional information
-      description: Add any other context or screenshots about the feature request here.
+      description: |
+        - Are you able to reliably reproduce the problem? How often does it occur? How many users are affected?
+        - Add any other context or screenshots about the feature here.
     validations:
       required: false

CODE_OF_CONDUCT.md .github/CODE_OF_CONDUCT.mdCODE_OF_CONDUCT.md renamed to .github/CODE_OF_CONDUCT.md

@@ -9,7 +9,7 @@ body:
         **HUBBERS!!** This is the github/docs open source repo. You may want to open an issue in the internal-only github/docs-content repo instead.
 
         * For questions, ask in [Discussions](https://github.com/github/docs/discussions).
-        * Before you file an issue read the [Contributing guide](https://github.com/github/docs/blob/main/CONTRIBUTING.md).
+        * Before you file an issue read the [Contributing guide](https://docs.github.com/en/contributing).
         * Check to make sure someone hasn't already opened a similar [issue](https://github.com/github/docs/issues).
 
   - type: checkboxes

CONTRIBUTING.md .github/CONTRIBUTING.mdCONTRIBUTING.md renamed to .github/CONTRIBUTING.md

@@ -35,11 +35,11 @@ body:
       label: Tasks
       description: Please be sure to complete each of the following.
       options:
-        - label: MUST follow our [general contributing guidelines](CONTRIBUTING.md) for voice and markup format.
+        - label: MUST follow our [general contributing guidelines](https://docs.github.com/en/contributing) for voice and markup format.
           required: true
         - label: MUST emphasize how the third-party product works with GitHub.
           required: true
-        - label: MUST be written in Markdown format, using [one of the templates provided](contributing/github-partners/README.md#templates).
+        - label: MUST be written in Markdown format, using [one of the templates provided](https://docs.github.com/en/contributing/writing-for-github-docs/templates).
           required: true
         - label: MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the `contributor.name` and `contributor.URL` properties in the template's YAML frontmatter.
           required: true
@@ -64,4 +64,4 @@ body:
     attributes:
       value: |
         Once all tasks are completed, please mention `@github/docs-content` for next steps.
-        /cc @github/partner-engineering for :eyes:.
+        /cc @github/technology-partnerships-and-engineering for :eyes:.