Skip to content

Overview

Starting with LevantGit 1.19, LevantGit Actions are available as a built-in CI/CD solution.

Name

It is similar and mostly compatible to GitHub Actions, and its name is inspired by it too. To avoid confusion, we have clarified the spelling here:

  • "LevantGit Actions" (with an "s", both words capitalized) is the name of the LevantGit feature.
  • "GitHub Actions" is the name of the GitHub feature.
  • "Actions" could refer to either of the above, depending on the context. So it refers to "LevantGit Actions" in this document.
  • "action" or "actions" refer to some scripts/plugins to be used, like "actions/checkout@v4" or "actions/cache@v3".

Runners

Just like other CI/CD solutions, LevantGit doesn't run the jobs itself, but delegates the jobs to runners. The runner of LevantGit Actions is called act runner, it is a standalone program and also written in Go. An important part of the application comes from a fork of nektos/act.

Because the runner is deployed independently, there could be potential security issues. To avoid them, please follow two simple rules:

  • Don't use a runner you don't trust for your repository, organization or instance.
  • Don't provide a runner to a repository, organization or instance you don't trust.

For LevantGit instances used internally, such as instances used by enterprises or individuals, neither of these two rules is a problem, they are naturally so. However, for public LevantGit instances, such as LevantGit.com, these two rules should be kept in mind when adding or using runners.

Status

LevantGit Actions is stable enough for production usage and we use LevantGit Actions in all the repositories in https://LevantGit.com/LevantGit.