> For the complete documentation index, see [llms.txt](https://cover-docs.diffblue.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cover-docs.diffblue.com/features/cover-pipeline/cover-pipeline-for-github/github-workflow.md).

# GitHub workflow

Integrating the Diffblue Cover Action into your CI/CD pipeline supports the software development workflow to provide AI automation of unit tests. The following provides an illustrative development workflow, with and without Cover Pipeline for GitHub, covering key steps to illustrate differences in workflow.

| Without Cover Pipeline for GitHub                                                                                        | With Cover Pipeline for GitHub                                                                                                                                                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A Java project with <mark style="color:red;">manually written</mark> tests.                                              | A Java project with <mark style="color:blue;">an AI created Java Unit Test Suite</mark>.                                                                                                                                                                   |
| A software developer makes a code change and <mark style="color:red;">manually updates</mark> the associated unit tests. | A software developer makes a code change - <mark style="color:blue;">no manual unit test update is needed</mark>.                                                                                                                                          |
| After a pull request, the code change and unit test change are <mark style="color:red;">manually reviewed</mark>.        | After a pull request, <mark style="color:blue;">the Diffblue Test Suite is automatically updated</mark>, and the code change and unit test change are reviewed. <mark style="color:blue;">The test diff assists with catching regressions and bugs.</mark> |
| After passing code review, the updated code and associated unit tests are merged.                                        | After passing code review, the updated code and associated unit tests are merged.                                                                                                                                                                          |

<div align="left"><figure><img src="/files/TKDUOKTmVfFdJvJB6BOT" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/D5eOfJkMjwSfV3y656HV" alt=""><figcaption></figcaption></figure></div>