How to read and merge a pull request when you don't code

• Repository: The place on GitHub that holds the code of your app.
• Branch: A separate copy of the code. The main branch usually goes to your live app.
• Commit: One saved change to the code.
• Check: An automatic test that runs on the change.
• Merge: The action that puts the change into the main branch.
• Conflict: Two changes to the same lines of code. GitHub cannot choose the correct change.

1. Open your repository on GitHub and click Pull requests.
2. Click the pull request.
3. Read the title and the description. The description must tell you what changed and why.
4. Read the checks near the bottom of the page.
5. Click Files changed and read the names of the files.
6. If the pull request has a preview link, open the link and do the main tasks of your app.

A green tick shows that a check passed. A red cross shows that a check failed. A yellow dot shows that a check did not finish.

In Files changed, green lines show new code. Red lines show removed code. A package update often changes thousands of lines in a lock file, such as package-lock.json. This is usual, and you do not need to read these lines.

Merge the pull request only if all of these conditions are true.

• The description agrees with the change that you asked for.
• All checks passed.
• The names of the files agree with the description.
• The main tasks of your app operate correctly in the preview, if a preview exists.

Do not merge the pull request and get help from a developer if one of these conditions is true.

• A check failed and you do not know why.
• The change touches sign-in, payments or the structure of the database, and you did not ask for this.
• The change removes tests.
• The change is a major update and your app has no tests.
• You see a password or a secret key in the changed lines.
• GitHub shows a message about conflicts.

1. Go to the bottom of the pull request.
2. Click Merge pull request.
3. Click Confirm merge.
4. Wait for your host to deploy the change.
5. Open the live app and do the main tasks.

The button can show Squash and merge or Rebase and merge. Each button puts the change into the main branch.

If your app is connected to Lovable, the change also goes to Lovable when you merge into the synced branch. Wait for the change to show in Lovable before you send a new prompt.

1. Open the merged pull request.
2. Go to the bottom of the page and click Revert.
3. GitHub makes a new pull request. Merge this new pull request.
4. Open the live app and do the main tasks.

If you do not see the button, you do not have write permission. Ask the administrator of the repository. GitHub has more information. A revert changes the code only. A revert does not change the data in your database.