Source Protection/Protect and publish

A protected copy, ready to ship.

Your repository stays exactly as it is. We publish a protected copy for your customer or vendor, with the parts you chose locked.

Publish · acme-platform

Your repository

acme/platform

Not changed

Protected copy

acme/platform-protected

3 files locked

mainreleaseOne commit

Publish

How publishing works.

Protect and publish makes a second copy of your repository in which the files you chose are locked and the rest is as you wrote it. Your own repository is not changed. You pick the target repository and the branches, and you can publish again whenever the map changes.

Pick where it goes

Choose a new or empty repository on GitHub, GitLab or Bitbucket, and the branches to publish.

The chosen files are locked

Every file on your map becomes a locked file in the copy. Everything else stays readable, so the project still reads like normal code.

Keep the history or start clean

Squash it into one commit, or keep the history with the locked files filtered out.

Keeping history keeps commit messages, so choose with that in mind.

Publish again any time

Change the map and publish again. Keys you already gave out keep working with the new builds of the repositories they cover.

Who uses it.

Software vendors preparing an on premises release
One protected copy goes to the customer. Your own repository never leaves.
Teams handing a codebase to an agency or contractor
They receive the project with your crown jewels locked.
Product companies shipping to several customers
Publish from one repository and give each customer their own key.