Composer VCS仓库包请求问题咨询（含自定义分支配置）

Hey there, let's work through this Composer problem step by step—forking packages and getting Composer to pick up your custom branches can be tricky, but we'll nail it down. First, let's recap what you've done to make sure we're aligned:

• Forked calebporzio/onboard to your mpjraaij/onboard repo
• Created a dev-bugfix branch with your changes
• Updated your root Laravel project's composer.json to reference your VCS repo and require the custom branch

Now let's go through the most common culprits and fixes:

1. Double-Check Your VCS Repository Config #

First, make sure your repositories entry is formatted correctly. No typos in the URL, and it should look like this (fill in your other repos where the ellipses are):

"repositories": [
    // ... your other repositories
    {
        "type": "vcs",
        "url": "https://github.com/mpjraaij/onboard"
    }
],

If your repo is private, note that Composer won't be able to pull it unless you set up authentication (we'll cover that later).

2. Fix the Branch Name <-> Composer Require String Mismatch #

This is a super common gotcha! Composer uses the dev- prefix to map to Git branches. So:

• If your branch is named bugfix, you'd require dev-bugfix
• If your branch is literally named dev-bugfix, you need to require dev-dev-bugfix

Double-check the actual branch name on your GitHub repo. If your branch is dev-bugfix, update your require line to:

"require": {
    // ... other packages
    "calebporzio/onboard": "dev-dev-bugfix"
},

That's easy to mix up, and it's the cause of this issue more often than not.

3. Don't Change the Package Name in Your Fork's Composer.json #

Make sure the composer.json in your mpjraaij/onboard repo's dev-bugfix branch still has "name": "calebporzio/onboard". If you changed it to your own username, Composer will treat it as a completely different package, so your require line for calebporzio/onboard won't match. Leave the name as the original—Composer uses the VCS repo to override where it pulls the package from, even if the name is the same as the original.

4. Clear Composer's Cache #

Composer caches a ton of metadata, and old cache can cause it to ignore your new repo or branch. Run these commands to wipe the cache and force a fresh fetch:

composer clear-cache
composer update calebporzio/onboard

5. Set Up Authentication (If Your Repo is Private) #

If your forked repo is private, Composer can't access it without authentication. You have two easy options:

• SSH: Use the SSH URL in your repositories entry (git@github.com:mpjraaij/onboard.git) and make sure your SSH key is linked to your GitHub account.
• Personal Access Token (PAT): Generate a PAT with repo access on GitHub, then run composer config github-oauth.github.com YOUR_TOKEN to save it, or use the token in the repo URL like https://YOUR_TOKEN@github.com/mpjraaij/onboard.git.

6. Update Composer to the Latest Version #

Outdated Composer versions sometimes have bugs with VCS repository handling. Run this to get the latest version:

composer self-update

7. Get Verbose Output to Diagnose the Exact Error #

If none of the above works, run Composer with verbose mode to see exactly what's going wrong:

composer update calebporzio/onboard -vvv

Look for lines like "Failed to clone repository" or "Could not find branch dev-bugfix"—these will tell you exactly where the problem is.

内容的提问来源于stack exchange，提问作者Maarten Raaijmakers