Awesome

<div align="center"> <a href="https://travis-ci.org/ramasilveyra/gitpkg?branch=master"> <img src="https://travis-ci.org/ramasilveyra/gitpkg.svg?branch=master" alt="Build Status"> </a> <a href="https://codecov.io/github/ramasilveyra/gitpkg?branch=master"> <img src="https://img.shields.io/codecov/c/github/ramasilveyra/gitpkg.svg?branch=master" alt="Codecoverage"> </a> </div> <h1 align="center">gitpkg</h1> <p align="center"><b>Publish packages as git tags</b></p> <p align="center"> 🔧 Works with projects with build steps.<br /> 👯 Works with projects with multiple packages (monorepos).<br /> 🏎 Lightweight git tags (only the files needed are included). </p> <h2 align="center">Table of Contents</h2>

Background
- Terminology
Install
Usage
- Publish
Contribute
Troubleshooting
License

<h2 align="center">Background</h2>

Both npm and yarn support installing packages from git tags.

But things can get difficult with packages that have a build step (eg babel) and monorepos with multiples packages (eg lerna).

gitpkg publish creates a git tag with the same files as if you were running npm publish or yarn publish and uploads the generated git tag to a git repository.

Also you can publish any gitpkg package to the same repository, so you can have only one repository used as common registry and you get away from your project git repository the git tags with the build code.

Terminology:

gitpkg package: git tag generated by gitpkg.
gitpkg registry: git repository used as common host for your gitpkg packages.

<h2 align="center">Install</h2>

Node.js v10.12 or newer is required.

npm registry

Via the yarn client:

$ yarn global add gitpkg

Via the npm client:

$ npm install -g gitpkg

gitpkg registry

Via the yarn client:

$ yarn global add ramasilveyra/public-registry#gitpkg-v1.0.0-beta.2-gitpkg

Via the npm client:

$ npm install -g ramasilveyra/public-registry#gitpkg-v1.0.0-beta.2-gitpkg

<h2 align="center">Usage</h2>

Publish

Publishes a package to a git repository, by default uploads the package to the git repository in the git remote origin (git remote -v to see your git remote origin url). The package published is defined by the package.json in the current directory.

$ gitpkg publish

See in action.

--registry, -r

$ gitpkg publish --registry git@mygit.server:org/private-registry.git

This flag tells gitpkg to publish the package to a specific gitpkg registry.

You can also set the gitpkg registry permanently by adding "gitpkg":{"registry":"git@mygit.server:org/private-registry.git"} to the package.json.

<h2 align="center">Configuration</h2>

You can also configure gitpkg with a config file. Create a file named gitpkg.config.js in the root of your project or in the root of a subpackage.

Available config settings

registry

Publish the package to a specific gitpkg registry. Same as the registry flag of the cli.

getTagName

Function used to create the git tags. The function receives one object pkg, which is the content of the package.json file.

// Example content of gitpkg.config.js
module.exports = () => ({
  registry: 'git@mygit.server:org/private-registry.git',
  getTagName: pkg => `${pkg.name}-v${pkg.version}-gitpkg`
});

<h2 align="center">Troubleshooting</h2>

Usage with Gerrit

gitpkg works by publishing tags that contain only the files in a package. The commits in these tags don't appear on any branch, so Gerrit will reject them by default:

! [remote rejected] …
    (prohibited by Gerrit: update for creating new commit object not permitted)

To gain the permission gitpkg needs, add Create Reference and Push entries to the refs/tags/* reference in the Access settings of your repository.

<h2 align="center">Contribute</h2>

Feel free to dive in! Open an issue or submit PRs.

gitpkg follows the Contributor Covenant Code of Conduct.

<h2 align="center">License</h2>