setup-bun VS changed-files

I use Bun in CI too, and they have a clean GitHub Action for it: https://github.com/oven-sh/setup-bun.

Actually now that you mention CI, I remember now that I did also run into non-deterministic problems runnign type checks on projects with Bun using Github's free runner.

Errors looked like this, but it worked fine every 2/3 runs with the exact same code:

We need to add two additional steps. The first one is to retrieve all new files, and the second one is to run the enhanced config only on the new files. In this example the third-party GitHub Action called changed-files is used to obtain the new files. In the GitHub Marketplace for Actions, there is a considerable number of similar actions with similar functionality. You can choose the one that suits you best, as the functionality is more or less the same for all of them.

I determined this after dozens of attempts working with the other GitHub Action, tj-actions/changed-files which feeds a list of modified files to clang-format-lint.

GitHub actions has actions that do similar, I’ve used this one before with great success: https://github.com/tj-actions/changed-files

You could also clean up your changed files job by using this (https://github.com/tj-actions/changed-files) or something similar. That would at least make it easier to understand what it's supposed to be doing. You can use it to get the directories containing any changed package.json files. Then use that output as as a matrix input.

View on GitHub