Continuous integration
Also called CI.
Continuous integration is the practice of committing code to a shared repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git. often, and building and testing those commits so errors show up sooner.
Example
You push a commitA commit records a project state in Git, plus history information such as the parent commit, the author, and a message. and open a pull requestA pull request asks people to review proposed code changes and combine them into a target branch.. A workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result. installs the project and runs its tests. The pull request shows whether those tests passed. You still decide whether to mergeA merge brings another branch’s snapshots onto the branch you are on, usually after a person agrees..
Why it matters
GitHub's docs define it that way. Committing more often leaves less new code to search when a test fails, and it makes changes from different people easier to combine. The tests can include linters, security checks, code coverage, functional tests, and other checks. Building and testing needs a computer. You can run the checks on your own machine before you push, or a CI server can watch the repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git. for new commits.
GitHub ActionsGitHub Actions is GitHub's continuous integration and continuous delivery platform. It automates checks such as building and testing a pull request. is one way to run that practice. A workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result. can build the code and run the tests on a machine GitHub hosts or one you host, when something happens in GitHub, such as a push, or on a schedule. GitHub shows those results on the pull requestA pull request asks people to review proposed code changes and combine them into a target branch.. The docs say that when all CI tests in a workflow pass, the changes are ready to be reviewed or merged, and that when a test fails, one of your changes may have caused the failure. A finished check is evidence about that run. Merging is still a separate decision.
How it shows up on bot.ski
On bot.ski, pull requests and pushes to main run a GitHub ActionsGitHub Actions is GitHub's continuous integration and continuous delivery platform. It automates checks such as building and testing a pull request. 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, and reading this page does not start a check.
Common confusion
Continuous integration is the practice. GitHub ActionsGitHub Actions is GitHub's continuous integration and continuous delivery platform. It automates checks such as building and testing a pull request. is a platform that can run it, and a workflowA workflow is a connected sequence of steps that takes a task from a starting input to an intended result. file is the configuration for one run. A passing check does not mergeA merge brings another branch’s snapshots onto the branch you are on, usually after a person agrees. the pull requestA pull request asks people to review proposed code changes and combine them into a target branch. by itself. A failed test does not by itself name the line that broke.
Sources
Updated October 3, 2026.