Skip to content

Make test_changes in CI smarter #834

@eskerda

Description

@eskerda

At the moment it runs any whole system that changed. It's common for systems to fail regularly, so this CI step can be annoying to contributors or force a PR to include unrelated changes for the sake of ✅

When the changes are on the json file and not the py file we should be checking only the instances that changed in particular and not the whole system.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions