You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -196,7 +196,7 @@ featuredLinks:
196
196
197
197
### `allowTitleToDifferFromFilename`
198
198
199
-
- Purpose: Indicates whether a page is allowed to have a title that differs from its filename. Pages with this frontmatter set to `true` will not be flagged in tests or updated by `script/reconcile-ids-with-filenames.js`. Use this value if a file's `title` frontmatter includes Liquid or punctuation that cannot be part of the filename. For example, the article "[About Enterprise Managed Users](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)" uses a Liquid reusable in its title, `'About {% data variables.product.prodname_emus %}'`, which cannot be in the filename, `about-enterprise-managed-users.md`, so the `allowTitleToDifferFromFilename` frontmatter is set to `true`.
199
+
- Purpose: Indicates whether a page is allowed to have a title that differs from its filename. Pages with this frontmatter set to `true` will not be flagged in tests or updated by `src/content-render/scripts/reconcile-filenames-with-ids.js`. Use this value if a file's `title` frontmatter includes Liquid or punctuation that cannot be part of the filename. For example, the article "[About Enterprise Managed Users](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)" uses a Liquid reusable in its title, `'About {% data variables.product.prodname_emus %}'`, which cannot be in the filename, `about-enterprise-managed-users.md`, so the `allowTitleToDifferFromFilename` frontmatter is set to `true`.
Copy file name to clipboardexpand all lines: content/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ If you would like to read more about debugging and troubleshooting the {% data v
67
67
68
68
### Using browser shortcuts
69
69
70
-
The [`script/bookmarklets`](https://github.com/github/docs/tree/main/script/bookmarklets) directory in the {% data variables.product.prodname_docs %} repository contains browser shortcuts that can help with reviewing {% data variables.product.company_short %} documentation. For more information, see the directory's [`README`](https://github.com/github/docs/tree/main/script/bookmarklets/README.md).
70
+
The [`src/bookmarklets`](https://github.com/github/docs/tree/main/src/bookmarklets) directory in the {% data variables.product.prodname_docs %} repository contains browser shortcuts that can help with reviewing {% data variables.product.company_short %} documentation. For more information, see the directory's [`README`](https://github.com/github/docs/tree/main/src/bookmarklets/README.md).
Copy file name to clipboardexpand all lines: content/contributing/setting-up-your-environment-to-work-on-github-docs/troubleshooting-your-environment.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ git push
34
34
35
35
## Troubleshooting local server problems
36
36
37
-
If you are running `script/server` and get a `Cannot find module` error, try the following command before restarting the server.
37
+
If you are running `npm start` and get a `Cannot find module` error, try the following command before restarting the server.
38
38
39
39
```shell
40
40
npm install
@@ -52,7 +52,7 @@ npm install
52
52
If you are having trouble with the staging server, you should see more information about the error in your browser or on the command line if you run the site locally. Check out your branch locally and use the following command to launch the local server.
53
53
54
54
```shell
55
-
script/server
55
+
npm start
56
56
```
57
57
58
58
When the server is running, navigate to the problematic article on `https://localhost:4000` in your browser. The staging server will just show an "Oops" error, but the local server should show a stack trace for debugging.
Copy file name to clipboardexpand all lines: content/contributing/writing-for-github-docs/using-yaml-frontmatter.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -188,7 +188,7 @@ featuredLinks:
188
188
189
189
### `allowTitleToDifferFromFilename`
190
190
191
-
- Purpose: Indicates whether a page is allowed to have a title that differs from its filename. For example, `content/rest/reference/orgs.md` has a title of `Organizations` instead of `Orgs`. Pages with this frontmatter set to `true` will not be flagged in tests or updated by `script/reconcile-ids-with-filenames.js`.
191
+
- Purpose: Indicates whether a page is allowed to have a title that differs from its filename. For example, `content/rest/reference/orgs.md` has a title of `Organizations` instead of `Orgs`. Pages with this frontmatter set to `true` will not be flagged in tests or updated by `src/content-render/scripts/reconcile-filenames-with-ids.js`.
192
192
- Type: `Boolean`. Default is `false`.
193
193
- Optional.
194
194
@@ -225,7 +225,7 @@ defaultTool: cli
225
225
### `learningTracks`
226
226
227
227
- Purpose: Render a list of learning tracks on a product's sub-landing page.
228
-
- type: `String`. This should reference learning tracks' names defined in [`data/learning-tracks/*.yml`](https://github.com/github/docs/tree/main/data/learning-tracks).
228
+
- Type: `String`. This should reference learning tracks' names defined in [`data/learning-tracks/*.yml`](https://github.com/github/docs/tree/main/data/learning-tracks).
Copy file name to clipboardexpand all lines: contributing/development.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ In a matter of minutes, you will be ready to edit, preview and test your changes
38
38
39
39
### Using browser shortcuts
40
40
41
-
The [`script/bookmarklets`](../script/bookmarklets) directory contains some browser shortcuts that can help with reviewing GitHub documentation. See [`script/bookmarklets/README.md`](../script/bookmarklets/README.md) for details.
41
+
The [`src/bookmarklets`](../src/bookmarklets) directory contains some browser shortcuts that can help with reviewing GitHub documentation. See [`src/bookmarklets/README.md`](../src/bookmarklets/README.md) for details.
Copy file name to clipboardexpand all lines: contributing/working-in-docs-repository.md
-2
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,4 @@ Here's some information that might be helpful while working on a Docs PR:
16
16
17
17
-[Liquid](/contributing/liquid-helpers.md) - We use liquid helpers to create different versions of our content.
18
18
19
-
-[Scripts](/script/README.md) - The scripts directory is the home for all of the scripts you can run locally.
20
-
21
19
-[Tests](/tests/README.md) - We use tests to ensure content will render correctly on the site. Tests run automatically in your PR, and sometimes it's also helpful to run them locally.
When you're looking at a page on docs.github.com or a preview server at preview.ghdocs.com, clicking this bookmarklet will load the same path you're viewing but on your local server running at localhost:4000.
When you're looking at a page on a preview server at preview.ghdocs.com or your local server running at localhost:4000, clicking this bookmarklet will load the same path you're viewing but on the live documentation site at docs.github.com.
When you're looking at a page on either docs.github.com, preview.ghdocs.com, or localhost:4000, clicking this bookmarklet will open the source Markdown file from your local checkout in VS Code.
33
33
34
34
The installation requires a few steps:
35
35
36
-
1. Copy the contents of [`script/bookmarklets/open-in-vscode.js`](./open-in-vscode.js).
36
+
1. Copy the contents of [`src/bookmarklets/open-in-vscode.js`](./open-in-vscode.js).
37
37
1. Browse to https://chriszarate.github.io/bookmarkleter/ and paste the code into the box.
38
38
1. Find the path of **your local checkout** of the docs repo you want to open files from (for example, `/Users/<USERNAME>/repos/docs`).
39
39
1. Paste the path in place of where it says `REPLACE_ME` in line 1 (make sure to leave the single quotes around it).
@@ -42,8 +42,8 @@ The installation requires a few steps:
This bookmarklet modifies the `Files changed` page of a GitHub pull request that has a current staging deployment. For each Markdown file in the diff view, it adds links to the preview deployment of the file for each version: `FPT / GHEC / GHES / AE`. (Some of these may redirect to another version or 404 if that version of the page doesn't exist.)
48
48
49
-
Note: readable JavaScript source lives in `script/bookmarklets/pr-link-source.js`. The bookmarklet code was generated via https://chriszarate.github.io/bookmarkleter.
49
+
Note: readable JavaScript source lives in `src/bookmarklets/pr-link-source.js`. The bookmarklet code was generated via https://chriszarate.github.io/bookmarkleter.
0 commit comments