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.
- What does a pull request from Rewalto contain?
- One branch, one commit and one description. The description carries the finding the change answers, the evidence behind it, why the change fixes it, and how to undo it. If the file it edits has moved since the finding was made, Rewalto refuses to open the pull request rather than guess.
- Why a pull request and not a direct change?
- Because your team already reviews, audits and rolls back pull requests. Review, history and undo come from a tool your developers use every day, instead of a new one Rewalto would have to invent. It is also why this is the lower-risk connector: Rewalto never holds a credential that changes your live site.
- GitHub's permission allows merging. Why should I trust that you won't?
- You are right that it allows it: GitHub's merge endpoint needs the same permission that committing a branch needs, so no scope lets a tool open a pull request while forbidding a merge. The guarantee is that the code to merge does not exist in the product, and a test fails if anyone adds it. If you want the permission itself constrained too, branch protection on your side does that.
- Will Rewalto move my site to Next.js?
- No. The connector opens pull requests on a repository that already exists. Migrating a site is a different conversation, at a different price.
- Which repositories can it see?
- Only the ones you select when you install the GitHub App. It cannot read a private repository outside that selection, and you add or remove repositories in your GitHub settings.
- 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.