Skip to content
This repository was archived by the owner on May 11, 2026. It is now read-only.
This repository was archived by the owner on May 11, 2026. It is now read-only.

correctly run the sanity checks #1

Description

@noah1510

Running the sanity check is the main blocker before tagging the code with v1.
At the moment running the sanity scripts seems to have a few problems that need to be solved:

  • figure out how to run the sanity checks only for the latest commit not for all changes
  • Find the best way to run the sanity checks between the commit and push (using bash or directly from python)
  • Enable the sanity checks by default and fail the action if they fail

The first point is the most problematic.
It is the reason why I set them to be optional.
At the moment when the sanity checks are run they will run on the whole wrapdb.
In other words they compile every project in the wrapdb.
I don't know why they do this and how to prevent it but it is a problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions