public-mirrors/composer
1
0
Fork 0
mirror of https://github.com/composer/composer synced 2025-05-08 16:17:37 +00:00
Code Activity

Make it explicitly clear that dev- shouldn't be in the actual branch name. (#10335)

Browse source
This commit is contained in:
Colan Schwartz 2021-12-07 15:22:17 -05:00 • committed by GitHub
parent a4a89f1508
commit 04dbed27a9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/05-repositories.md
View file

@ -342,8 +342,9 @@ project to use the patched version. If the library is on GitHub (this is the
case most of the time), you can fork it there and push your changes to case most of the time), you can fork it there and push your changes to
your fork. After that you update the project's `composer.json`. All you have your fork. After that you update the project's `composer.json`. All you have
to do is add your fork as a repository and update the version constraint to to do is add your fork as a repository and update the version constraint to
point to your custom branch. In `composer.json`, you should prefix your custom point to your custom branch. In `composer.json` only, you should prefix your
branch name with `"dev-"`. For version constraint naming conventions see custom branch name with `"dev-"` (without making it part of the actual branch
name). For version constraint naming conventions see
[Libraries](02-libraries.md) for more information. [Libraries](02-libraries.md) for more information.
Example assuming you patched monolog to fix a bug in the `bugfix` branch: Example assuming you patched monolog to fix a bug in the `bugfix` branch: