Illustration of Marisa demonstrating the process of Checking Out Pull Requests from Forked Remotes in Git, symbolizing the swift integration of important updates into a project's workflow.

Welcome to another installment of TWIL, the weekly knowledge boost from Cuttlesoft where we showcase the practical insights our team members discover. In this week’s edition, Marisa offers a clear guide on how to Checkout Pull Requests from Forked Remotes in Git. Learn the step-by-step process to incorporate changes swiftly, even before they're merged upstream—perfect for times when updates can't wait.

Checkout pull request from forked remote

Say you have a library you are using, and there's an issue with it. A fix has been pull-requested, but it hasn't been merged in. We should:

  1. Fork the library
  2. Set the upstream
  3. Checkout the PR locally
  4. Push up our branch
  5. Set the source for the library as our forked branch

Fork the library for Cuttlesoft

git clone <cuttlesoft-library-url>
git remote add upstream <library-url>
git fetch upstream pull/<PR-ID>/head:<new-branch-name>
git checkout <new-branch-name>
git push origin <new-branch-name>

Get the url for the commit pushed up to our Cuttlesoft fork, it should look like:

https://github.com/cuttlesoft/<library-name>#<commit-hash>

Update your package.json with the url like so:

"<library-name>": "https://github.com/cuttlesoft/<library-name>#<commit-hash>",

Make sure you yarn install or npm i and you should be good to go!

  • Git
Marisa Gomez's profile picture
Marisa Gomez

Senior Software Engineer

Related Posts

Illustration of a small, determined knight in weathered medieval armor and a bucket helmet, wearing a tattered red cape, striding across barren cracked earth with sword drawn, surrounded by a swirling cloud of scattered wooden alphabet letters representing Token Guard, a GitHub Action that monitors and guards against token context bloat in AI coding agent workflows by counting the tokens in LLM instruction files committed to repositories."
February 10, 2026 • Frank Valcarcel

Token Guard: Keeping Your Agent Context Lean in CI

Token Guard is a GitHub Action that counts tokens in your agent context files and enforces limits in CI. Here’s why we check agent context into our repos, and why keeping it lean matters for team collaboration.

Software engineer reviewing code during a code audit, analyzing source code on a monitor alongside documentation in a modern office environment.
February 18, 2025 • Frank Valcarcel

How We Review and Audit Software

A thorough code audit goes beyond automated scanners. Here is how we evaluate security, architecture, maintainability, compliance, and what you can expect when you work with us.

Let's work together

Tell us about your project and how Cuttlesoft can help. Schedule a consultation with one of our experts today.

Contact Us