Workflows

GitHub Actions uses the concept of workflows, which are scripts that run automatically whenever a specific event occurs (e.g. pushing a commit).

Each GitHub Actions workflow is defined in a .yml file in the .github/workflows directory. For information on workflows, check the following docs:

Shared workflows

Some workflows are shared across repositories.

Caution

The shared workflows are automatically synced (from the org-wide-files repo). You should thus not manually change their contents.

General workflows

Track-specific workflows

  • configlet: checks if the track's (configuration) files are properly structured - both syntactically and semantically
  • No important files changed: comments on pull requests that would cause re-testing of existing solutions
  • Test: verify the track's exercises

Tooling-specific workflows

  • Deploy: deploy the track tooling Docker image to Docker Hub and ECR

Optional workflows

There are also some workflows that tracks might opt-into:

Custom workflows

Maintainers are free to add custom workflows to their repos. Examples of such workflows could be: