kroshu/kuka_drivers

Evaluate GitHub actions for pipeline builds

resizoltan opened this issue · 3 comments

Industrial CI also runs on GitHub actions. Main reason to consider switching: Travis-CI does not support skipping builds if only certain files or directories have changed (travis-ci/travis-ci#6301). This would be quite relevant for the documentation folder - it makes no sense to trigger a build when updating it.

I fully support this. I've read the same about skipping builds.

PR into master, great! :) Can we consider this as closed? All builds are migrated? Or are there any left out?

It's only done for this repo, and it's still sitting on prepare-for-open-collab branch. When we have an initial somewhat-ready state, we can merge to master imo.