How to Maintain UPM Package Part 3

Managing a forked repository

As the time of writing, 20% of packages published on the OpenUPM platform are forked from upstream repositories. One popular reason to fork a repository is that the original author doesn’t have time to maintain a UPM package. In this article, we’ll discuss how to maintain a forked repository efficiently.

Table of Contents

∘ Syncing with upstream repository automatically
∘ Version control
∘ Conclusions

I suggest below branch pattern to manage a fork,

Create the upm-convert branch.

Make necessary changes to add UPM support to the upm-convert branch. There’re many good tutorials around the Internet, so we will just cover the basics.

Add file .github/pull.yml as below.

The version control strategy can be various depends on the upstream repository.

If the upstream doesn’t have any version control, or you have dramatically changed the repository content, you can create your versions.

If the upstream already has version control, it’s better to keep consistent with it. But how to present your changes to an existing upstream version? Two tactics:

Related posts:

Robert Brendler on skills that empower individuals.. Tell us briefly about your journey — where did you study, work and what are you doing at the moment?.

Most major cryptocurrencies have started the new year on a positive note. However, in the past 24 hours, the crypto markets are witnessing a sea of red. This shows that the rally has hit a roadblock…

Beaucoup de personnes aiment les secrets, ils aiment être dans la confidence, dans les secrets des dieux. Ils aiment en parler, plus encore, ils aiment en discuter. Mais ceci n’est valable que pour…