Integrations

# Next.js integration

A pull request on your repository, opened for a person to review.

STATUS
:   Available

ACCESS
:   Read, and a proposal to review

REMOVING IT
:   One click, any time

## What lands

A pull request on the repository you name: one branch, one commit, one description carrying the finding it answers.

## What we can reach

Read

- The repository's contents, on the repositories you select.

Write

- A branch, a commit, and a pull request. Nothing else.

## What we never do

- Push to a default branch.
- Merge its own pull request — no code in the product calls GitHub's merge endpoint, checked by a test that parses the connector for a `.Merge()` call or a `/merge` URL literal.
- Touch a repository you did not select, or read a private repository outside the selection.

## Removing it

Revoke the GitHub App in your organisation's settings. It takes effect immediately and open pull requests stay as ordinary ones you own.

## Questions

Does Rewalto integrate with Next.js?
:   Yes. A GitHub App scoped to contents and pull requests, on the repositories you select. It opens a branch, a commit and a pull request; a person on your team reviews and merges it.

Can Rewalto merge its own pull request?
:   No. GitHub's merge endpoint needs exactly the same permission committing a branch already needs, so no scope forbids merging while permitting a pull request. The guarantee is that no code in the product calls that endpoint, which a test checks by parsing the connector for a merge call.

How do I remove the connector?
:   Revoke the GitHub App in your organisation's settings. It takes effect immediately, and any open pull request stays as an ordinary one you own.

## Not seeing yours, or have a question?

A proposal is a diff and a description, so any system that accepts one can take it. Tell us what you use.

[Contact us](https://rewalto.com/contact)