Skip to content

split change detector action into a separate job, or a separate workflow completely #2736

Closed

Description

Split change detector action into a separate job, or a separate workflow completely main due to the following reasons:

  • the coverage report job does not need to wait for change detector (which takes much longer, and doesn't utilize caching), currently it is blocked when change detector is running.
  • extra if statements in the test-and-upload-coverage.yml workflow for a different flow (no code coverage steps).
  • test-and-upload-coverage.yml is getting more complex and caching stuff doesn't apply to change detector either.
  • optimize change detector when it is it's own job or workflow (perhaps using caching in a different way).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    ci/buildThis is issue is about the build or CI system, and the administration of it.code qualityRelated to improving code quality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions