Hacker News new | past | comments | ask | show | jobs | submit login

The CI file can specify what triggers different workflows.

https://docs.github.com/en/actions/using-workflows/triggerin...

    on:
      pull_request:
        types:
          - opened
        paths:
          - '.github/workflows/**'
          - '.github/CODEOWNERS'
          - 'package*.json'
That triggers when those files change.

The "get them all to run in a single repo" is the challenge of the monorepo. The trade off is "if you change a common library, how do you trigger the test suites in all of the downstream repos to run with the new common library and verify that they still work?"

With a monorepo, that second part is solved for you... at the cost of needing to solve the problem that you're asking about.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: