d6f733f577
Bumps [bleach](https://github.com/mozilla/bleach) from 3.1.0 to 3.3.0. - [Release notes](https://github.com/mozilla/bleach/releases) - [Changelog](https://github.com/mozilla/bleach/blob/master/CHANGES) - [Commits](https://github.com/mozilla/bleach/compare/v3.1.0...v3.3.0) Signed-off-by: dependabot[bot] <support@github.com> |
||
|---|---|---|
| .github/workflows | ||
| script | ||
| src | ||
| tests | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| requirements.txt | ||
| setup.py | ||
| tasks.py | ||
carboncopy
Keep your repositories up-to-date with their templates in a few keystrokes.
❓ Why carboncopy?
Github Template Repositories made it really easy to skip project boilerplate setup steps and to produce "new project kits" that ensure that all your (or your organization's) new projects have all the must-haves. Problem is, templates aren't set in stone and it's likely that templates get updated after some projects have been spawned from it.
Because template repositories are different than forks, you can't simply rebase your project to gulp in the latest templated goodies -- leaving you with the gnarly task of manually moving files over. No more.
With carboncopy, you are one command away from pulling in the latest changes from your template repositories as if it were a regular base branch. You can configure it via its RC file to ignore certain files from the template, and more!
📦 Installation
It's easy as 1, 2, 3!
pip install carboncopy
🔨 Usage
From your repository, simply type carboncopy in your terminal to bring up a prompt asking you what to pull from your template repository. Any change made is left as an unstaged change so you can commit and merge it however you want.
⚙ Configuration
You can configure the way carboncopy handles your template's contents by creating a .carboncopyrc file at the root of your repository. Documentation TBD. See src/carboncopy/config_defaults.py for general layout.