funador

Joined 8 years ago

Karma

Submissions

Member since

Oct 5

[email protected]

View on Hacker News

Recent submissions

Comment · 3 months ago

I do have a pretty heavy pipe line of local tests and running more than one of those at once is what spurred me to write this package. Especially the build step.

Comment · 3 months ago

That looks like a much slicker version, will check that out

Comment · 3 months ago

There are a ton of places this package would not be suitable :)

I have not used this on a team, and what you would end up with is likely a giant PR with all those local commits that no one wants to review. Eventually someone might hold their nose and press the approve button. But that would probably be the end of the package at that workplace.

This is optimized for one engineer that does not have the machine capacity to run multiple lanes of their check test suites locally at once and also does want to pay for GHA minutes on a free plan to run those suites in the cloud.

Comment · 3 months ago

Definitely not reviewing the code when 90 commits go in a day :)

I have local test suite of unit / arch / e2e / build / lint / tsc when it merges to dev. Then the same suite runs on a merge to main which pushes to prod. I have post main-push e2e that checks for regressions and automatically rolls back.

Each suite run takes 3-4 minutes so I can usually push through 15 or so commits an hour fully tested and cleanly.

I do not use PRs with this workflow, and if something breaks I add tests to prevent it happening again rather than altering the setup.