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

add tests that validate if we break any of our getting started guides #486

Open
2 of 3 tasks
TheWebTech opened this issue Jul 17, 2023 · 0 comments
Open
2 of 3 tasks

Comments

@TheWebTech
Copy link
Contributor

Is your feature request related to a problem? Please describe.

We have numerous getting started guides, from themes, to modules, to serverless. Each references the boilerplate since the boilerplate keeps current with our best practices. If file names change, or a file is deleted that causes pain for a developer following that tutorial.

Describe the solution you'd like

Add tests that activate in GitHub PRs. Check:

  • Does a specific file name exist at specific location.

Open to other test ideas, this is just the most basic I can think of that would get us pretty far for the most common type of update.

When a PR changes a file name or moves a file, we need to notify the dev doc tech writer team to update docs.

Checklist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant