Pull Request Generation

🌱 Soon available: Custom Pull Request templates are coming! You’ll be able to define how Snapr structures and writes PR descriptions — tailoring their tone, format, and content to perfectly match your project’s standards.

How it works

Snapr can generate Pull Requests by following a standard development workflow: an Issue is created, and a Pull Request is then generated to address it.

1. The trigger

A developer comments @snapr develop on an Issue. That comment fires a webhook that instantly notifies Snapr to start working on the request.

2. The reaction

Snapr receives the event and launches a Kubernetes Job, a short-lived worker responsible for generating the new Pull Request.

3. The analysis

Inside the Job, Snapr:

Reads the Issue description and its conversation history
Extracts relevant context, requirements, and goals
Optionally asks for clarification if more information is needed

4. The generation

Using that context, Snapr:

Creates a new branch for the feature or fix
Generates the corresponding code changes
Opens a Pull Request addressing the original Issue

4. The feedback

Once the Pull Request is created, Snapr takes ownership of it, actively maintaining and refining the changes as the review progresses.

Whenever new comments or change requests appear, Snapr:

Reviews the feedback from maintainers and reviewers
Updates the code accordingly if required.
Pushes new commits directly to the same PR.

This ensures that the Pull Request stays up-to-date, aligned with feedback, and ready to merge without manual intervention.