Difference between #12 and #13 of
Using your own forked version of extensions with composer

Changes

Title unchanged

Using your own forked version of extensions with composer

Category unchanged

Tutorials

Yii version unchanged

Tags unchanged

yii2, composer, fork, extension, repository, update, package

Content changed

[...]
### Step 1
Let's take an example. Let's say you want to fork the package [`kartik-v/yii2-widgets`](https://github.com/kartik-v/yii2-widgets).

### Step 2
Fork the library on GitHub. It is important for you to check if the source contains a valid `composer.json` file. This is important for the rest of the steps to work. After the fork, let's say your forked package version is now at `https://github.com/yourname/yii2-widgets`. As a next step, you must create a custom branch (you will update the version constraint in `composer.json` later to point to your custom branch). Your custom branch name must be prefixed with `dev-`. For example, let us assume you create a branch named `custom` and your patched updates will be within a branch named `dev-custom`.

### Step 3
Push your library changes to the custom branch above (You can check which one it is on Packagist, under “Source:” – [Example](https://packagist.org/packages/kartik-v/yii2-widgets)).

### Step 4
[...]
3 2
40 followers
Viewed: 23 606 times
Version: 2.0
Category: Tutorials
Tags: composer, extension, fork, package, repository, update, yii2
Written by: Kartik V
Last updated by: Kartik V
Created on: May 7, 2014
Last updated: 8 years ago
Update Article
Revert to #12 | Revert to #13

Revisions

View all history