# @xarunoba/ccoco 🥥

![Static Badge](https://img.shields.io/badge/Made_with-%E2%9D%A4%EF%B8%8F-red?style=for-the-badge) [![License](https://img.shields.io/npm/l/%40xarunoba%2Fccoco?style=for-the-badge)](https://github.com/xarunoba/ccoco?tab=MIT-1-ov-file#readme)
[![NPM Version](https://img.shields.io/npm/v/%40xarunoba%2Fccoco?style=for-the-badge&logo=npm)](https://www.npmjs.com/package/@xarunoba/ccoco?activeTab=readme)

**`ccoco`** — change config on checkout

Change your configurations on checkout for easy environment change. Integrate with git hooks.

## Why

My team didn't want to populate the `package.json` too much with scripts so I created a tool that can easily replace the main config files whenever a branch changed.
`ccoco` initially started as a tool specifically used for the Node.js ecosystem but has been rewritten to Go for platform independence. You can use `ccoco` for any kinds of projects as long as it is within a Git repository.

## More Details

For more details visit the [GitHub repository](https://github.com/xarunoba/ccoco).