> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/remediate/fixes-on-developer-pull-requests.md).

# Fixes on Developer Pull Requests

Konvu fixes vulnerable dependencies in pull requests your developers open, after a short quiet period.

When a developer opens a pull request, Konvu can check it for vulnerable dependencies and commit a fix to the same branch. The developer gets the fix in the pull request they are already working on, instead of a separate fix pull request later.

{% hint style="info" %}
This feature is turned on per organization. Contact your Konvu team to enable it.
{% endhint %}

## How it works

1. A developer opens a pull request on a connected repository.
2. Konvu waits for a **30-minute quiet period**, so it does not commit on top of a developer who is still pushing changes.
3. If the pull request is still open, Konvu checks it for vulnerable dependencies and prepares a fix.
4. Konvu commits the fix to the pull request's branch.

## Which pull requests are eligible

* A person opened the pull request. Pull requests opened by bots, such as Dependabot, are skipped.
* It is still open after the quiet period. A pull request merged or closed in the meantime is skipped.
* The repository is connected through the Konvu GitHub App and is active in Konvu.

## Limits

* Dependency fixes only. Konvu does not commit code fixes for SAST findings to developer pull requests.
* GitHub only.
* The fix follows the same rules as a [fix pull request](/konvu/triage-and-remediation/remediate/fix-pull-requests.md#limitations): version upgrades to stable releases, with no overrides or pins.


---

# 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://docs.konvu.com/konvu/triage-and-remediation/remediate/fixes-on-developer-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.