Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repo sync #1429

Merged
merged 1 commit into from
Nov 18, 2020
Merged

repo sync #1429

merged 1 commit into from
Nov 18, 2020

Conversation

Octomerger
Copy link
Contributor

This is an automated pull request to sync changes between the public and private repos.

🤖 This pull request should be merged (not squashed) to preserve continuity across repos, so please let a bot do the merging!

@Octomerger Octomerger merged commit f8e0f73 into main Nov 18, 2020
@Octomerger Octomerger deleted the repo-sync branch November 18, 2020 11:55
@github-actions
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours.

This was referenced Jan 17, 2022
This was referenced Jan 18, 2022
jnidzwetzki pushed a commit to jnidzwetzki/docs that referenced this pull request Oct 6, 2022
Clean up some messes in scripts, frontmatter, and troubleshooting that
will make things more extensible and maintainable later:

- Rename the `_scripts` directory to `.helper-scripts`. This establishes
  a convention around 'hidden' directories: Directories that start with
  an underscore are part of the Gatsby build but not built as pages in
  their own right. These should be copied over to the web-documentation
  repo when the build runs. Directories that start with a period should
  not be seen by Gatsby at all. These should be ignored when copying
  files into the web-documentation repo. (Note this describes ideal
  future behavior, not current behavior, which is more ad hoc.)

- Change all `.mdx` files to `.md`. This standardizes linting and link
  checking across the files. Note that partial imports still need to use
  the `.mdx` extension, because the build process changes `.md` files to
  `.mdx` behind the scenes.

- Convert the `product` (singular) key in troubleshooting frontmatter to
  `products` (plural). More extensible as we can imagine troubleshooting
  items that relate to multiple products.

Co-authored-by: Lana Brindley <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants