| Name | cruft JSON |
| Version |
2.15.0
JSON |
| download |
| home_page | |
| Summary | Allows you to maintain all the necessary cruft for packaging and building projects separate from the code you intentionally write. Built on-top of CookieCutter. |
| upload_time | 2023-05-11 06:49:11 |
| maintainer | |
| docs_url | None |
| author | Timothy Crosley |
| requires_python | >=3.7 |
| license | MIT |
| keywords |
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
[](https://cruft.github.io/cruft/)
_________________
[](http://badge.fury.io/py/cruft)
[](https://anaconda.org/conda-forge/cruft)
[](https://github.com/cruft/cruft/actions?query=workflow%3A%22Run+tests%22+branch%3Amaster)
[](https://codecov.io/gh/cruft/cruft)
[](https://github.com/psf/black)
[](https://timothycrosley.github.io/isort/)
[](https://gitter.im/cruft/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](https://pypi.python.org/pypi/cruft/)
[](https://pepy.tech/project/cruft)
#### Trending Contributors
[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/0)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/1)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/2)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/3)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/4)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/5)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/6)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/7)
_________________
[Read Latest Documentation](https://cruft.github.io/cruft/) - [Browse GitHub Code Repository](https://github.com/cruft/cruft/)
_________________
**cruft** allows you to maintain all the necessary boilerplate for packaging and building projects separate from the code you intentionally write.
Fully compatible with existing [Cookiecutter](https://github.com/cookiecutter/cookiecutter) templates.
Creating new projects from templates using cruft is easy:
And, so is updating them as the template changes overtime:
Many project template utilities exist that automate the copying and pasting of code to create new projects. This *seems* great! However, once created, most leave you with that copy-and-pasted code to manage through the life of your project.
cruft is different. It automates the creation of new projects like the others, but then it also helps you to manage the boilerplate through the life of the project. cruft makes sure your code stays in-sync with the template it came from for you.
## Key Features
* **Cookiecutter Compatible**: cruft utilizes [Cookiecutter](https://github.com/cookiecutter/cookiecutter) as its template expansion engine. Meaning it retains full compatibility with all existing [Cookiecutter](https://github.com/cookiecutter/cookiecutter) templates.
* **Template Validation**: cruft can quickly validate whether or not a project is using the latest version of a template using `cruft check`. This check can easily be added to CI pipelines to ensure your projects stay in-sync.
* **Automatic Template Updates**: cruft automates the process of updating code to match the latest version of a template, making it easy to utilize template improvements across many projects.
## Installation
To get started - install `cruft` using a Python package manager:
`pip3 install cruft`
OR
`poetry add cruft`
OR
`pipenv install cruft`
## Creating a New Project
To create a new project using cruft run `cruft create PROJECT_URL` from the command line.
For example:
cruft create https://github.com/timothycrosley/cookiecutter-python/
cruft will then ask you any necessary questions to create your new project. It will use your answers to expand the provided template, and then return the directory it placed the expanded project.
Behind the scenes, cruft uses [Cookiecutter](https://github.com/cookiecutter/cookiecutter) to do the project expansion. The only difference in the resulting output is a `.cruft.json` file that
contains the git hash of the template used as well as the template variables specified.
## Updating a Project
To update an existing project, that was created using cruft, run `cruft update` in the root of the project.
If there are any updates, cruft will have you review them before applying. If you accept the changes cruft will apply them to your project
and update the `.cruft.json` file for you.
!!! tip
Sometimes certain files just aren't good fits for updating. Such as test cases or `__init__` files. You can tell cruft to always skip updating these files on a project by generating project with `--skip cruft/__init__.py --skip tests` arguments or manually adding them to a skip section within your `.cruft.json` file:
{
"template": "https://github.com/timothycrosley/cookiecutter-python",
"commit": "8a65a360d51250221193ed0ec5ed292e72b32b0b",
"skip": [
"cruft/__init__.py",
"tests"
],
...
}
Or, if you have toml installed, you can add skip files directly to a `tool.cruft` section of your `pyproject.toml` file:
[tool.cruft]
skip = ["cruft/__init__.py", "tests"]
Note that it is possible to use glob patterns for selecting the files to skip:
{
"skip": [
"**/__init__.py",
"tests/*"
],
...
}
## Updating Values of Template Variables
`cruft` can also be used to update a project to use new values of template variables; avoiding the need to regenerate
the project from sratch using `cookiecutter`.
For example, imagine a project that was initially generated some while ago, and then later on, you want to change the
values of some of the template variables, e.g. to change `use_some_feature` to `"yes"` or to change `project_name` to
`"new-project-name"`.
There are 2 ways this can be done, as described below.
### Update Variables via the Command Line
You can perform the update directly via the command line if you have only a handful of simple variables.
This will change `use_some_feature` to `"yes"` while leaving all other variables unchanged:
```bash
cruft update --variables-to-update '{ "use_some_feature" : "yes" }'
```
This will change both `use_some_feature` to `"yes"` and `project_name` to `"new-project-name"` (and still leaving all
other variables unchanged):
```bash
cruft update --variables-to-update '{ "use_some_feature" : "yes", "project_name" : "new-project-name" }'
```
The provided argument must be a valid JSON string (i.e. using double quotes, no trailing comma etc.).
### Update Variables via a Cruft File
If you prefer to use and editor or you have many or complex variables, you can also perform the changes via providing an
updated .cruft.json.
```bash
# copy the existing cruft file to a temporary location (outside of your repo)
cp .cruft.json ~/tmp/new-cruft.json
# edit the file using your faviourite editor
edit ~/tmp/new-cruft.json
# perform the update
# (this will also update your original .cruft.json automatically)
cruft update --variables-to-update-file ~/tmp/new-cruft.json
```
## Checking a Project
Checking to see if a project is missing a template update is as easy as running `cruft check`. If the project is out-of-date an error and exit code 1 will be returned.
`cruft check` can be added to CI pipelines to ensure projects don't unintentionally drift.
## Linking an Existing Project
Have an existing project that you created from a template in the past using Cookiecutter directly? You can link it to the template that was used to create it using: `cruft link TEMPLATE_REPOSITORY`.
For example:
cruft link https://github.com/timothycrosley/cookiecutter-python/
You can then specify the last commit of the template the project has been updated to be consistent with, or accept the default of using the latest commit from the template.
## Compute the diff
With time, your boilerplate may end up being very different from the actual cookiecutter template. Cruft allows you to quickly see what changed in your local project compared to the template. It is as easy as running `cruft diff`. If any local file differs from the template, the diff will appear in your terminal in a similar fashion to `git diff`.
The `cruft diff` command optionally accepts an `--exit-code` flag that will make cruft exit with a non-0 code should any diff is found. You can combine this flag with the `skip` section of your `.cruft.json` to make stricter CI checks that ensures any improvement to the template is always submitted upstream.
## Automating updates with GitHub Actions
If you have many repositories to manage, you can automate the change detection process with GitHub Actions. This example runs every Monday at 2am UTC and creates a new pull request if there are changes detected which a maintainer can accept or reject. It creates two PRs - one to pull in the new files to the repository and one to update the `.cruft.json` file only, which has the effect of rejecting the change from the upstream repository.
> Since Jan 2022, registries/organisations must explicitly grant the authority to create a pull request. This can be enabled on a per-organisation level, or a per-registry level for personal projects. See [GitHub](https://github.blog/changelog/2022-05-03-github-actions-prevent-github-actions-from-creating-and-approving-pull-requests/) for more details.
```yaml
# /.github/workflows/cruft-update.yml
name: Update repository with Cruft
permissions:
contents: write
pull-requests: write
on:
schedule:
- cron: "0 2 * * 1" # Every Monday at 2am
jobs:
update:
runs-on: ubuntu-latest
strategy:
fail-fast: true
matrix:
include:
- add-paths: .
body: Use this to merge the changes to this repository.
branch: cruft/update
commit-message: "chore: accept new Cruft update"
title: New updates detected with Cruft
- add-paths: .cruft.json
body: Use this to reject the changes in this repository.
branch: cruft/reject
commit-message: "chore: reject new Cruft update"
title: Reject new updates detected with Cruft
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: "3.10"
- name: Install Cruft
run: pip3 install cruft
- name: Check if update is available
continue-on-error: false
id: check
run: |
CHANGES=0
if [ -f .cruft.json ]; then
if ! cruft check; then
CHANGES=1
fi
else
echo "No .cruft.json file"
fi
echo "has_changes=$CHANGES" >> "$GITHUB_OUTPUT"
- name: Run update if available
if: steps.check.outputs.has_changes == '1'
run: |
git config --global user.email "you@example.com"
git config --global user.name "GitHub"
cruft update --skip-apply-ask --refresh-private-variables
git restore --staged .
- name: Create pull request
if: steps.check.outputs.has_changes == '1'
uses: peter-evans/create-pull-request@v4
with:
token: ${{ secrets.GITHUB_TOKEN }}
add-paths: ${{ matrix.add-paths }}
commit-message: ${{ matrix.commit-message }}
branch: ${{ matrix.branch }}
delete-branch: true
branch-suffix: timestamp
title: ${{ matrix.title }}
body: |
This is an autogenerated PR. ${{ matrix.body }}
[Cruft](https://cruft.github.io/cruft/) has detected updates from the Cookiecutter repository.
```
## Why Create cruft?
Since I first saw videos of [quickly](https://www.youtube.com/watch?v=9EctXzH2dss) being used to automate Ubuntu application creation, I've had a love/hate relationship with these kinds of tools.
I've used them for many projects and certainly seen them lead to productivity improvements. However, I've always felt like they were a double-edged sword. Sure, they would automate away the copying and pasting many would do to create projects. However, by doing so,
they encouraged more code to be copied and pasted! Then, over time, you could easily be left with hundreds of projects that contained copy-and-pasted code with no way to easy way to update them. I created cruft to be a tool that recognized that balance between project creation and maintenance and provided mechanisms to keep built projects up-to-date.
I hope you too find `cruft` useful!
~Timothy Crosley
Raw data
{
"_id": null,
"home_page": "",
"name": "cruft",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "",
"author": "Timothy Crosley",
"author_email": "timothy.crosley@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/d8/59/bb9e052fba37972e4b27db74d0bc770bade501d48336dec3c89fe57e9513/cruft-2.15.0.tar.gz",
"platform": null,
"description": "[](https://cruft.github.io/cruft/)\n_________________\n\n[](http://badge.fury.io/py/cruft)\n[](https://anaconda.org/conda-forge/cruft)\n[](https://github.com/cruft/cruft/actions?query=workflow%3A%22Run+tests%22+branch%3Amaster)\n[](https://codecov.io/gh/cruft/cruft)\n[](https://github.com/psf/black)\n[](https://timothycrosley.github.io/isort/)\n[](https://gitter.im/cruft/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n[](https://pypi.python.org/pypi/cruft/)\n[](https://pepy.tech/project/cruft)\n\n#### Trending Contributors\n\n[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/0)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/1)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/2)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/3)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/4)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/5)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/6)[](https://sourcerer.io/fame/samj1912/cruft/cruft/links/7)\n_________________\n\n[Read Latest Documentation](https://cruft.github.io/cruft/) - [Browse GitHub Code Repository](https://github.com/cruft/cruft/)\n_________________\n\n**cruft** allows you to maintain all the necessary boilerplate for packaging and building projects separate from the code you intentionally write.\nFully compatible with existing [Cookiecutter](https://github.com/cookiecutter/cookiecutter) templates.\n\nCreating new projects from templates using cruft is easy:\n\n\n\nAnd, so is updating them as the template changes overtime:\n\n\n\nMany project template utilities exist that automate the copying and pasting of code to create new projects. This *seems* great! However, once created, most leave you with that copy-and-pasted code to manage through the life of your project.\n\ncruft is different. It automates the creation of new projects like the others, but then it also helps you to manage the boilerplate through the life of the project. cruft makes sure your code stays in-sync with the template it came from for you.\n\n## Key Features\n\n* **Cookiecutter Compatible**: cruft utilizes [Cookiecutter](https://github.com/cookiecutter/cookiecutter) as its template expansion engine. Meaning it retains full compatibility with all existing [Cookiecutter](https://github.com/cookiecutter/cookiecutter) templates.\n* **Template Validation**: cruft can quickly validate whether or not a project is using the latest version of a template using `cruft check`. This check can easily be added to CI pipelines to ensure your projects stay in-sync.\n* **Automatic Template Updates**: cruft automates the process of updating code to match the latest version of a template, making it easy to utilize template improvements across many projects.\n\n## Installation\n\nTo get started - install `cruft` using a Python package manager:\n\n`pip3 install cruft`\n\nOR\n\n`poetry add cruft`\n\nOR\n\n`pipenv install cruft`\n\n\n## Creating a New Project\n\nTo create a new project using cruft run `cruft create PROJECT_URL` from the command line.\n\nFor example:\n\n cruft create https://github.com/timothycrosley/cookiecutter-python/\n\ncruft will then ask you any necessary questions to create your new project. It will use your answers to expand the provided template, and then return the directory it placed the expanded project.\nBehind the scenes, cruft uses [Cookiecutter](https://github.com/cookiecutter/cookiecutter) to do the project expansion. The only difference in the resulting output is a `.cruft.json` file that\ncontains the git hash of the template used as well as the template variables specified.\n\n## Updating a Project\n\nTo update an existing project, that was created using cruft, run `cruft update` in the root of the project.\nIf there are any updates, cruft will have you review them before applying. If you accept the changes cruft will apply them to your project\nand update the `.cruft.json` file for you.\n\n!!! tip\n Sometimes certain files just aren't good fits for updating. Such as test cases or `__init__` files. You can tell cruft to always skip updating these files on a project by generating project with `--skip cruft/__init__.py --skip tests` arguments or manually adding them to a skip section within your `.cruft.json` file:\n\n {\n \"template\": \"https://github.com/timothycrosley/cookiecutter-python\",\n \"commit\": \"8a65a360d51250221193ed0ec5ed292e72b32b0b\",\n \"skip\": [\n \"cruft/__init__.py\",\n \"tests\"\n ],\n ...\n }\n\n Or, if you have toml installed, you can add skip files directly to a `tool.cruft` section of your `pyproject.toml` file:\n\n [tool.cruft]\n skip = [\"cruft/__init__.py\", \"tests\"]\n \n Note that it is possible to use glob patterns for selecting the files to skip:\n {\n \"skip\": [\n \"**/__init__.py\",\n \"tests/*\"\n ],\n ...\n }\n\n## Updating Values of Template Variables\n\n`cruft` can also be used to update a project to use new values of template variables; avoiding the need to regenerate\nthe project from sratch using `cookiecutter`.\n\nFor example, imagine a project that was initially generated some while ago, and then later on, you want to change the\nvalues of some of the template variables, e.g. to change `use_some_feature` to `\"yes\"` or to change `project_name` to\n`\"new-project-name\"`.\n\nThere are 2 ways this can be done, as described below.\n\n### Update Variables via the Command Line\n\nYou can perform the update directly via the command line if you have only a handful of simple variables.\n\nThis will change `use_some_feature` to `\"yes\"` while leaving all other variables unchanged:\n```bash\ncruft update --variables-to-update '{ \"use_some_feature\" : \"yes\" }'\n```\n\nThis will change both `use_some_feature` to `\"yes\"` and `project_name` to `\"new-project-name\"` (and still leaving all\nother variables unchanged):\n```bash\ncruft update --variables-to-update '{ \"use_some_feature\" : \"yes\", \"project_name\" : \"new-project-name\" }'\n```\n\nThe provided argument must be a valid JSON string (i.e. using double quotes, no trailing comma etc.).\n\n### Update Variables via a Cruft File\n\nIf you prefer to use and editor or you have many or complex variables, you can also perform the changes via providing an\nupdated .cruft.json.\n\n```bash\n# copy the existing cruft file to a temporary location (outside of your repo)\ncp .cruft.json ~/tmp/new-cruft.json\n\n# edit the file using your faviourite editor\nedit ~/tmp/new-cruft.json\n\n# perform the update\n# (this will also update your original .cruft.json automatically)\ncruft update --variables-to-update-file ~/tmp/new-cruft.json\n```\n\n## Checking a Project\n\nChecking to see if a project is missing a template update is as easy as running `cruft check`. If the project is out-of-date an error and exit code 1 will be returned.\n`cruft check` can be added to CI pipelines to ensure projects don't unintentionally drift.\n\n\n## Linking an Existing Project\n\nHave an existing project that you created from a template in the past using Cookiecutter directly? You can link it to the template that was used to create it using: `cruft link TEMPLATE_REPOSITORY`.\n\nFor example:\n\n cruft link https://github.com/timothycrosley/cookiecutter-python/\n\nYou can then specify the last commit of the template the project has been updated to be consistent with, or accept the default of using the latest commit from the template.\n\n## Compute the diff\n\nWith time, your boilerplate may end up being very different from the actual cookiecutter template. Cruft allows you to quickly see what changed in your local project compared to the template. It is as easy as running `cruft diff`. If any local file differs from the template, the diff will appear in your terminal in a similar fashion to `git diff`.\n\nThe `cruft diff` command optionally accepts an `--exit-code` flag that will make cruft exit with a non-0 code should any diff is found. You can combine this flag with the `skip` section of your `.cruft.json` to make stricter CI checks that ensures any improvement to the template is always submitted upstream.\n\n## Automating updates with GitHub Actions\n\nIf you have many repositories to manage, you can automate the change detection process with GitHub Actions. This example runs every Monday at 2am UTC and creates a new pull request if there are changes detected which a maintainer can accept or reject. It creates two PRs - one to pull in the new files to the repository and one to update the `.cruft.json` file only, which has the effect of rejecting the change from the upstream repository.\n\n> Since Jan 2022, registries/organisations must explicitly grant the authority to create a pull request. This can be enabled on a per-organisation level, or a per-registry level for personal projects. See [GitHub](https://github.blog/changelog/2022-05-03-github-actions-prevent-github-actions-from-creating-and-approving-pull-requests/) for more details.\n\n```yaml\n# /.github/workflows/cruft-update.yml\nname: Update repository with Cruft\npermissions:\n contents: write\n pull-requests: write\non:\n schedule:\n - cron: \"0 2 * * 1\" # Every Monday at 2am\njobs:\n update:\n runs-on: ubuntu-latest\n strategy:\n fail-fast: true\n matrix:\n include:\n - add-paths: .\n body: Use this to merge the changes to this repository.\n branch: cruft/update\n commit-message: \"chore: accept new Cruft update\"\n title: New updates detected with Cruft\n - add-paths: .cruft.json\n body: Use this to reject the changes in this repository.\n branch: cruft/reject\n commit-message: \"chore: reject new Cruft update\"\n title: Reject new updates detected with Cruft\n steps:\n - uses: actions/checkout@v3\n\n - uses: actions/setup-python@v4\n with:\n python-version: \"3.10\"\n\n - name: Install Cruft\n run: pip3 install cruft\n\n - name: Check if update is available\n continue-on-error: false\n id: check\n run: |\n CHANGES=0\n if [ -f .cruft.json ]; then\n if ! cruft check; then\n CHANGES=1\n fi\n else\n echo \"No .cruft.json file\"\n fi\n\n echo \"has_changes=$CHANGES\" >> \"$GITHUB_OUTPUT\"\n\n - name: Run update if available\n if: steps.check.outputs.has_changes == '1'\n run: |\n git config --global user.email \"you@example.com\"\n git config --global user.name \"GitHub\"\n\n cruft update --skip-apply-ask --refresh-private-variables\n git restore --staged .\n\n - name: Create pull request\n if: steps.check.outputs.has_changes == '1'\n uses: peter-evans/create-pull-request@v4\n with:\n token: ${{ secrets.GITHUB_TOKEN }}\n add-paths: ${{ matrix.add-paths }}\n commit-message: ${{ matrix.commit-message }}\n branch: ${{ matrix.branch }}\n delete-branch: true\n branch-suffix: timestamp\n title: ${{ matrix.title }}\n body: |\n This is an autogenerated PR. ${{ matrix.body }}\n\n [Cruft](https://cruft.github.io/cruft/) has detected updates from the Cookiecutter repository.\n```\n\n## Why Create cruft?\n\nSince I first saw videos of [quickly](https://www.youtube.com/watch?v=9EctXzH2dss) being used to automate Ubuntu application creation, I've had a love/hate relationship with these kinds of tools.\nI've used them for many projects and certainly seen them lead to productivity improvements. However, I've always felt like they were a double-edged sword. Sure, they would automate away the copying and pasting many would do to create projects. However, by doing so,\nthey encouraged more code to be copied and pasted! Then, over time, you could easily be left with hundreds of projects that contained copy-and-pasted code with no way to easy way to update them. I created cruft to be a tool that recognized that balance between project creation and maintenance and provided mechanisms to keep built projects up-to-date.\n\nI hope you too find `cruft` useful!\n\n~Timothy Crosley\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Allows you to maintain all the necessary cruft for packaging and building projects separate from the code you intentionally write. Built on-top of CookieCutter.",
"version": "2.15.0",
"project_urls": null,
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "6f3c394d7446f306cdec0ec422f1673203b231ec3badc6bf6747174a12ee611a",
"md5": "a3501e74f79ab030378b83e89fafae4c",
"sha256": "2c1c6c7c512b8bc3afc66cefa829247dc067409a78ba2609d629d413444bc153"
},
"downloads": -1,
"filename": "cruft-2.15.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "a3501e74f79ab030378b83e89fafae4c",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 26086,
"upload_time": "2023-05-11T06:49:09",
"upload_time_iso_8601": "2023-05-11T06:49:09.372789Z",
"url": "https://files.pythonhosted.org/packages/6f/3c/394d7446f306cdec0ec422f1673203b231ec3badc6bf6747174a12ee611a/cruft-2.15.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "d859bb9e052fba37972e4b27db74d0bc770bade501d48336dec3c89fe57e9513",
"md5": "6c3ee8f6fe3a83ded21e87f84c5f2ba7",
"sha256": "9802af66037418655e7e4b6f30b531591e0761939b3ff5dd45d27c3a3f588abe"
},
"downloads": -1,
"filename": "cruft-2.15.0.tar.gz",
"has_sig": false,
"md5_digest": "6c3ee8f6fe3a83ded21e87f84c5f2ba7",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 23966,
"upload_time": "2023-05-11T06:49:11",
"upload_time_iso_8601": "2023-05-11T06:49:11.392652Z",
"url": "https://files.pythonhosted.org/packages/d8/59/bb9e052fba37972e4b27db74d0bc770bade501d48336dec3c89fe57e9513/cruft-2.15.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-05-11 06:49:11",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "cruft"
}
