-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy path.cookiecutter-replay.json
36 lines (36 loc) · 4.55 KB
/
.cookiecutter-replay.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
{
"cookiecutter": {
"Introduction": "",
"type": "lib",
"name": "dispatch-client",
"description": "Dispatch API client for Python",
"title": "Frequenz Dispatch Client Library",
"keywords": "dispatch, client, api, python",
"github_org": "frequenz-floss",
"license": "MIT",
"author_name": "Frequenz Energy-as-a-Service GmbH",
"author_email": "floss@frequenz.com",
"python_package": "frequenz.client.dispatch",
"pypi_package_name": "frequenz-client-dispatch",
"github_repo_name": "frequenz-client-dispatch-python",
"default_codeowners": "@frequenz-floss/api-dispatch-team",
"_template": "gh:frequenz-floss/frequenz-repo-config-python",
"_repo_dir": "/home/marenz/.cookiecutters/frequenz-repo-config-python/cookiecutter"
},
"_cookiecutter": {
"Introduction": "]\n\n Welcome to repo-config Cookiecutter template!\n\n This template will help you to create a new repository for your project. You will be asked to provide some information about your project.\n\n Here is an explanation of what each variable is for and will be used for:\n\n * `type`: The type of repository. It must be chosen from the list.\n\n* `name`: The name of the project. This will be used to build defaults for\n other inputs, such as `title`, `python_package`, etc. It should be one word,\n using only alphanumeric characters (and starting with a letter). It can\n include also `_` and `-` which will be handled differently when building\n other variables from it (replaced by spaces in titles for example).\n\n* `description`: A short description of the project. It will be used as the\n description in the `README.md`, `pyproject.toml`, `mkdocs.yml`, etc.\n\n* `title`: A human-readable name or title for the project. It will be used in\n the `README.md`, `CONTRIBUTING.md`, and other files to refer to the project,\n as well as the site title in `mkdocs.yml`.\n\n* `keywords`: A comma-separated list of keywords that will be used in the\n `pyproject.toml` file. If left untouched, it will use only some predefined\n keywords. If anything else is entered, it will be **added** to the default\n keywords.\n\n* `github_org`: The GitHub handle of the organization where the project will\n reside. This will be used to generate links to the project on GitHub.\n\n* `license`: Currently, only two options are provided: `MIT`, which should be\n used for open-source projects, and `Proprietary`, which should be used for\n closed-source projects. This will be added to file headers and used as the\n license in `pyproject.toml`.\n\n* `author_name`, `author_email`: The name and email address of the author of\n the project. They will be used in the copyright notice in file headers and\n as the author in `pyproject.toml`.\n\n* `python_package`: The Python package in which this project will reside. All\n files provided by this project should be located in this package. This needs\n to be a list of valid Python identifiers separated by dots. The source file\n structure will be derived from this. For example, `frequenz.actor.example`\n will generate files in `src/frequenz/actor/example`.\n\n* `pypi_package_name`: The name of the PyPI/wheel/distribution package. This\n should be consistent with the `python_package`, usually replacing `.` with\n `-`. For example, `frequenz-actor-example`.\n\n* `github_repo_name`: The handle of the GitHub repository where the project\n will reside. This will be used to generate links to the project on GitHub and\n as the top-level directory name.\n\n* `default_codeowners`: A space-separated list of GitHub teams (`@org/team`) or\n users (`@user`) that will be the default code owners for this project. This\n will be used to build the `CODEOWNERS` file. Please refer to the [code owners\n documentation] for more details on the valid syntax.\n\n[code owners documentation]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners\n\n\n [Please press any key to continue",
"type": "lib",
"name": "dispatch-client",
"description": "Dispatch API client for Python",
"title": "Frequenz Dispatch Client Library",
"keywords": "dispatch, client, api, python",
"github_org": "frequenz-floss",
"license": "MIT",
"author_name": "Frequenz Energy-as-a-Service GmbH",
"author_email": "floss@frequenz.com",
"python_package": "frequenz.client.dispatch",
"pypi_package_name": "frequenz-client-dispatch",
"github_repo_name": "frequenz-client-dispatch-python",
"default_codeowners": "@frequenz-floss/api-dispatch-team"
}
}