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.

Sign up for GitHub

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

Jump to bottom

Ensure we have one scenario per automation file #379

Merged
merged 1 commit into from
Sep 4, 2024
Merged

Ensure we have one scenario per automation file #379

merged 1 commit into from
Sep 4, 2024

Commits on Sep 4, 2024

  1. Ensure we have one scenario per automation file 

    This is in addition to a coming PR, #375. This change here is allowing
to ensure we follow those practices:
- only one scenario per file
- filename matches "scenario_name.yaml" pattern
    @cjeanner
    cjeanner committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    ab9c91e View commit details
    Browse the repository at this point in the history