Skip to content

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

@TheWebTech

Description

@TheWebTech

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions