hectorsector
commented
5 years ago I think we've already done this, but let's double check that we incorporated marketing's edits from https://github.com/github/marketing-content/issues/200
Closed hectorsector closed 5 years ago
hectorsector
commented
5 years ago I think we've already done this, but let's double check that we incorporated marketing's edits from https://github.com/github/marketing-content/issues/200
From CircleCI:
“Once you've written code, how do you ensure it's bug free? GitHub makes use of continuous integration (CI)—a requirement in modern software development when developers integrate code into a shared repository several times a day. Even better, adding automated tests and controls to your pipeline saves you time and gives your team improved reliability.”
This isn’t a great explanation or description of continuous integration. “Automated tests” is not an “even better” addition—it’s literally the point of CI/CD. Something like this would make a bit more sense, IMO:
In modern software development, developers integrate code into a shared repository several times a day. With such frequent code changes, how do you ensure your code is bug-free? Continuous Integration (CI) is an approach to software development in which tests run automatically anytime code is changed, saving you time and giving your team improved reliability. Continuous Deployment or Delivery (CD) refers to whatever happens after these tests run. If they pass, your new code can be automatically deployed to production, with the help of a CI/CD platform like CircleCI.