Pull Requests

A pull request proposes merging the changes on one branch into another — usually the default branch — and gives your team a place to review, discuss, and approve them before the merge happens.

Create a Branch

Work on a new branch so your changes stay separate from the default branch until they’re ready.

In the UI:

1. Open your repository and select the branch selector near the top-left (it shows the current branch name).
2. Type a new branch name in the search box and select Create Branch.

Locally:

1. Create and switch to the branch: git checkout -b feature-x
2. Make your changes, then stage and commit them: git add . then git commit -m "Describe what changed"
3. Push the branch to PlaidCloud Git: git push -u origin feature-x

Open a Pull Request

1. Open your repository and select the Pull Requests tab, then New Pull Request.
2. Set the compare branch to your feature branch and the base branch to the target (usually main or master).
3. Write a clear title and a description that explains what changed and why.
4. To link related issues, add a closing keyword in the description — for example, Closes #12 — so the issue closes automatically when the pull request merges.
5. Assign reviewers if needed, then select Create Pull Request.

Review Changes

Reviewers work through the pull request without merging anything:

1. Open the pull request and select Files Changed to read the diff.
2. Select any line in the diff to leave an inline comment on that specific change.
3. When finished, submit an overall verdict: Approve to sign off, or Request Changes to ask for revisions first.
4. The author pushes more commits to the same branch to address feedback — the pull request updates automatically, with no need to open a new one.
5. Reviewers mark individual comment threads as resolved once each concern is addressed.

Note

A repository administrator can enable branch protection on the default branch to require a minimum number of approvals before a pull request can be merged.

Merge

Once the pull request is approved:

1. Choose a merge method from the dropdown next to the Merge button:
   • Create a merge commit — preserves the full branch history with a merge commit.
   • Squash and merge — combines all commits on the branch into a single commit on the target branch.
   • Rebase and merge — replays the branch’s commits onto the target branch without a merge commit.
2. Select Merge to complete it.
3. Optionally select Delete Branch to clean up the feature branch once it’s no longer needed.

Next Steps

• Work with Repositories
• Track Work with Issues
• Organize Work with Project Boards