Can the concept of CI (Continuous Integration) be explained in the context of CI/CD practice?

Continuous Integration (CI) is the practice of frequently merging code changes from different developers into a shared repository. Each commit is automatically verified through builds and tests to quickly identify errors and conflicts.

In the context of CI/CD (Continuous Integration and Continuous Deployment), CI is responsible for automatic code verification and integration, while CD handles automatic delivery of tested code to testing or production environments.

Example: a developer pushes changes to the repository — an automatic build and tests are triggered (CI). If everything passes successfully, the changes are automatically deployed to a test server (CD). This accelerates the development cycle and improves product quality.