{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicszsxx2tr6pafgsvfscwgjxziy3rr44bkrchynkxthsbqhauckpu",
    "uri": "at://did:plc:wszrgoqdwy3i2dfeub2mt3wf/app.bsky.feed.post/3mho6dxo73id2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiash42xjj7kaex3pasxqgku7p6any6flttcqqkm65vchl77sgysnq"
    },
    "mimeType": "image/png",
    "size": 57009
  },
  "description": "How to configure lazy.nvim to reference a Pull Request for a given plugin.",
  "path": "/posts/2026/03/22/lazy-nvim-pr/",
  "publishedAt": "2026-03-22T18:18:03.000Z",
  "site": "https://www.jvt.me",
  "tags": [
    "blogumentation",
    "neovim",
    "codecompanion.nvim",
    "mcphub.nvim",
    "couple",
    "options",
    "I'd posted about on one of the PRs",
    "using the Git refs for PRs"
  ],
  "textContent": "As I did an update earlier on my Neovim plugins, I noticed a breaking change from codecompanion.nvim hadn't yet been addressed upstream with mcphub.nvim, but fortunately a couple of options were contributed by the community.\n\nUntil the PRs are merged, I wanted a way to pull the changes into my local setup with lazy.nvim, so I could continue using MCPHub.\n\nAs I'd posted about on one of the PRs, we can take advantage of using the Git refs for PRs, and then tell Lazy to use that branch.\n\nThis allows you to specify - as a one-time thing - the ref fetching for the given plugin:\n\n\n    git config remote.origin.fetch '+refs/pull/*:refs/remotes/origin/pull/*'\n\n\nThen from here, you can tell Lazy to use that PR branch:\n\n\n    return {\n      \"ravitemer/mcphub.nvim\",\n      branch = \"pull/279/merge\"\n    }\n\n\n(Note that you want to use `pull/279/merge` so it doesn't break when the PR is merged - or maybe you do want that, and instead want to use `pull/279/head`, for the forked repo's head branch)",
  "title": "Pointing lazy.nvim to a Pull Request",
  "updatedAt": "2026-03-22T18:18:03.000Z"
}