Continuous integration was coined as an extreme programming practice, but is used more loosely today.
Continuous integration was originally coined as an extreme programming practice, which states that code should be merged into the primary codebase every few hours.
It tends to be used a little more loosely today to reflect a DevOps practice of automating the process of integrating code into the main codebase.
This automation often includes checks to ensure the code can be safely merged. This includes programmatic tests, like unit tests or acceptance tests. But checks go far beyond running tests. Here are a few more examples:
The primary goal is to ensure that the code is ready to be merged into the main branch of the code, and to be consumed by other developers working on the project.
Commit file changes created during a GitHub automated workflow run.
A punchlist of the last few tasks for developers to consider before launching a new website.
With its large collection of (free) professional imagery and easy-to-use developer API, Unsplash is a great tool for generating contextual placeholder images for your application.