Skip to main content

Team Collaboration Tutorial

Learn how to use Pull Requests for team design reviews.

Time: 10 minutes Difficulty: Intermediate

Why PRs for Design?​

Pull Requests enable:

  • Review before merge - Team reviews changes first
  • Discussion - Comments on specific changes
  • History - Record of who changed what and why
  • Approval - Required sign-off before merging

Workflow Overview​

Designer A → Feature branch → PR → Review → Merge → main

Step 1: Create Feature Branch​

  1. Make sure you're on main
  2. Pull latest changes
  3. Open Branch, choose New branch, and create feature/updated-colors

Step 2: Make Changes​

  1. Switch to your feature branch
  2. Modify tokens as needed
  3. Push changes to the branch

Step 3: Create Pull Request​

  1. Push your commits to the feature branch
  2. Click Create pull request (it appears below the Commit section on any branch other than main)
  3. Fill in:
    • Title: "Update primary colors for accessibility"
    • Description: Explain why and what changed
    • Base: main

Step 4: Review Process​

On GitHub:

  1. Reviewers see the PR
  2. They can view changed files
  3. Leave comments or approve
  4. Request changes if needed

Step 5: Address Feedback​

If changes requested:

  1. Make edits in Figma
  2. Push again to same branch
  3. PR updates automatically

Step 6: Merge​

Once approved:

  1. Merge PR on GitHub
  2. Switch to main in GitFig
  3. Pull to get merged changes

Tips for Good PRs​

  • Keep changes focused
  • Write clear descriptions
  • Reference related issues
  • Include before/after context