Reusable GitHub Actions for S-CORE CI/CD automation. For reusable workflows, see the score_cicd-workflows repository.
inter-repo-access: resolve one auth mode and configure git for consistent cross-repository access.setup-qnx-sdp: setup QNX SDP environment for CI/CD workflows.setup-bazel-cache: configure Bazel caching with opinionated defaults.unblock-user-namespace-for-linux-sandbox: allow Bazel'slinux-sandboxto create user namespaces on Ubuntu runners.prune-cache: keep only the newest GitHub Actions cache generation per cache family and Git ref, deleting older ones.warm-bazel-repository-cache: warm Bazel repository cache for configured variants.
Most actions have a self-test workflow in the .github/workflows directory (test-*.yml) that exercises the action in a real runner environment. These workflows are reusable (workflow_call) and are executed from the PR workflow.
While it's possible to call actions in the same repository, as witnessed by the self-tests, it is not (easily) possible to do that from a reusable workflow. Since reusable workflows are a key part of our strategy for sharing CI/CD logic, we place the actions in a separate repository to ensure they can be used from any workflow in any repository.
Yes! However, testing is focused on the eclipse-score use case. Forks and private copies of S-CORE should work fine. GitHub Server and GitHub Data Residency are untested, so compatibility is not guaranteed — we welcome fixes but cannot offer support for those environments.