> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/~/revisions/SGhJfnCIOpxRjx1gC1k5/aikido-autofix/automatic-creation-of-pull-requests.md).

# Automatic Creation of Pull Requests

Aikido allows for automatic PR creation on a **daily basis**, handling mass upgrades of different versions through lockfile updates. Fine tune the Pull Request title, label and other settings with "PR Configuration"

{% hint style="warning" %}
Automatic creation is currently available for dependencies, containers and pentest autofixes.
{% endhint %}

### Setup automatic creation <a href="#setup-automatic-creation" id="setup-automatic-creation"></a>

**Step 1:** Go to [Autofix Settings](https://app.aikido.dev/issues/fix/settings) page

**Step 2:** Scroll down to Automated PRs. Enable the toggle for 'Autocreation of PRs'<br>

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2F3mpJkwi7GwZjzPc6DQ3C%2Fimage.png?alt=media&amp;token=7099003c-6fae-491a-b106-c8f71c18cb61" alt=""><figcaption></figcaption></figure>

**Step 3:** The configuration modal opens. You can enable autocreation for dependencies in code repos, automated fixes for Docker containers or automatically fix pentest issues. Make sure to select code repositories and containers for which you want PRs created.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2FiMLt9UzhYrqhq2NgbOaD%2Fimage.png?alt=media&amp;token=3fd5c2cb-817b-4942-8c1b-8fbdc8f86f9b" alt=""><figcaption></figcaption></figure>

**Step 4:** Test whether new PRs are created correctly by clicking the **Test Autocreation** button.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2FvReuPYbcFTyMW3btVQgb%2Fimage.png?alt=media&amp;token=1ef3fc2e-18fe-4fef-86bc-723ee96bef68" alt=""><figcaption></figcaption></figure>

## Pull Request Configuration <a href="#pull-request-configuration" id="pull-request-configuration"></a>

You can configure the AutoFix pull requests to your own needs with the ["PR Configuration" settings](https://app.aikido.dev/issues/fix/settings). It's possible to change the following fields:

* **Title Prefix:** Customize the title to match your internal processes
* **Label:** Add specific labels to the PR for easier sorting and tracking
* **Branch Syntax:** Customize the prefix of the branch Autofix creates
* **Commit Message Prefix:** Customize the message added to the PR
* **Summary:** Optionally include an additional message for each PR. For example add custom instructions for engineers or additional context.
* **Create Task for PR:** important for compliance reasons. This will automatically create a new task in your connected task tracker, linking to the created PR.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/~/revisions/SGhJfnCIOpxRjx1gC1k5/aikido-autofix/automatic-creation-of-pull-requests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.