Skip to content

Trigger CIs Based On PR Title #18

Description

@D-Alessian

The idea here would be to have the lint-pr CI be the root of all the other CIs, and run only certain types of checks based on the type of changes being introduced.

There is no need to check compilation if the docs are being changed. There is no need to check for typos in .md files if we're refactoring.

This WOULD require some kind of CI to check that the changes made are allowed based on the type of change.

  • DOCS: Only code comments and .md, .txt, or other pure text files.
  • CI: Only changes to the src/tools directory and .github (might need a bit more flexibility, but that would be the idea)
  • STYLE: Only changes to .prettierrc, or the eslint configs
    ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions