|
| 1 | +* `type`: The type of repository. It must be chosen from the list. |
| 2 | + |
| 3 | +* `name`: The name of the project. This will be used to build defaults for |
| 4 | + other inputs, such as `title`, `python_package`, etc. It should be one word, |
| 5 | + using only alphanumeric characters (and starting with a letter). |
| 6 | + |
| 7 | +* `description`: A short description of the project. It will be used as the |
| 8 | + description in the `README.md`, `pyproject.toml`, `mkdocs.yml`, etc. |
| 9 | + |
| 10 | +* `title`: A human-readable name or title for the project. It will be used in |
| 11 | + the `README.md`, `CONTRIBUTING.md`, and other files to refer to the project, |
| 12 | + as well as the site title in `mkdocs.yml`. |
| 13 | + |
| 14 | +* `keywords`: A comma-separated list of keywords that will be used in the |
| 15 | + `pyproject.toml` file. If left untouched, it will use only some predefined |
| 16 | + keywords. If anything else is entered, it will be **added** to the default |
| 17 | + keywords. |
| 18 | + |
| 19 | +* `github_org`: The GitHub handle of the organization where the project will |
| 20 | + reside. This will be used to generate links to the project on GitHub. |
| 21 | + |
| 22 | +* `license`: Currently, only two options are provided: `MIT`, which should be |
| 23 | + used for open-source projects, and `Proprietary`, which should be used for |
| 24 | + closed-source projects. This will be added to file headers and used as the |
| 25 | + license in `pyproject.toml`. |
| 26 | + |
| 27 | +* `author_name`, `author_email`: The name and email address of the author of |
| 28 | + the project. They will be used in the copyright notice in file headers and |
| 29 | + as the author in `pyproject.toml`. |
| 30 | + |
| 31 | +* `python_package`: The Python package in which this project will reside. All |
| 32 | + files provided by this project should be located in this package. This needs |
| 33 | + to be a list of valid Python identifiers separated by dots. The source file |
| 34 | + structure will be derived from this. For example, `frequenz.actor.example` |
| 35 | + will generate files in `src/frequenz/actor/example`. |
| 36 | + |
| 37 | +* `pypi_package_name`: The name of the PyPI/wheel/distribution package. This |
| 38 | + should be consistent with the `python_package`, usually replacing `.` with |
| 39 | + `-`. For example, `frequenz-actor-example`. |
| 40 | + |
| 41 | +* `github_repo_name`: The handle of the GitHub repository where the project |
| 42 | + will reside. This will be used to generate links to the project on GitHub and |
| 43 | + as the top-level directory name. |
| 44 | + |
| 45 | +* `default_codeowners`: A space-separated list of GitHub teams (`@org/team`) or |
| 46 | + users (`@user`) that will be the default code owners for this project. This |
| 47 | + will be used to build the `CODEOWNERS` file. Please refer to the [code owners |
| 48 | + documentation] for more details on the valid syntax. |
| 49 | + |
| 50 | +[code owners documentation]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners |
0 commit comments