# 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/j9SxbAe0YYv67GkpepFn" alt=""><figcaption></figcaption></figure></div>

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cover-docs-preview.diffblue.com/features/cover-pipeline/cover-pipeline-for-github/github-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.