GitHub Actions
Also called GitHub CI.
GitHub Actions is GitHub's continuous integrationContinuous integration is the practice of committing code to a shared repository often, and building and testing those commits so errors show up sooner. and continuous delivery platform. It automates checks such as building and testing a pull requestA pull request asks people to review proposed code changes and combine them into a target branch..
Example
Someone opens a pull requestA pull request asks people to review proposed code changes and combine them into a target branch.. A GitHub Actions workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result. builds the project and runs its tests, and the pull request shows whether those checks passed. Merging is still a separate decision.
Why it matters
GitHub's docs say you configure a workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result. in a YAML file in the repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git.. An event, such as opening a pull requestA pull request asks people to review proposed code changes and combine them into a target branch., can start that workflow. The workflow has jobs, and each job runs on a runner, which is a machine GitHub provides or one you host. People say CI for the continuous integrationContinuous integration is the practice of committing code to a shared repository often, and building and testing those commits so errors show up sooner. part: build and test proposed changes before they land.
GitHub also uses the same platform for continuous delivery, such as deploying after a mergeA merge brings another branch’s snapshots onto the branch you are on, usually after a person agrees.. A green check is evidence about that run. It is not, by itself, the decision to merge.
How it shows up on bot.ski
On bot.ski, pull requests and pushes to main run a GitHub Actions workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result. in this repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git.. The workflow installs dependencies, typechecks, lints, runs the unit tests, and builds the site. It does not deployTo deploy is to make a version of software available where it can run or be served, such as a preview, a test system, or production.. The public website does not show that run or a build log, and reading this page does not start a check. The AutomationAutomation is software carrying out work according to rules or triggers, so a person does not repeat the same action by hand. and Workflow glossary pages also cite GitHub's Actions docs.
Common confusion
GitHub Actions is the platform. An action is one reusable step inside a workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result.. CI names the habit of building and testing changes as they are proposed. The glossary word Workflow is any connected sequence of steps, not only a YAML file on GitHub.
Sources
Updated October 2, 2026.