Prompts¶
When you create a package, you are prompted to enter these values.
Templated Values¶
The following appear in various parts of your generated project.
full_name¶
Your full name.
email¶
Your email address.
github_username¶
Your GitHub username.
project_name¶
The name of your new Python package project. This is used in documentation, so spaces and any characters are fine here.
git_project_name¶
The name of the GitHub project repository you have created.
If it is the same as your project_name but with hyphens instead of spaces leave this blank. Your GitHub repository name will be generated with hyphens.
If its different enter your project GitHub repository name here.
project_slug¶
The namespace of your Python package. This should be Python import-friendly. Typically, it is the slugified version of project_name. Note: your PyPi project will use project_slug, so change those in the README afterwards.
project_short_description¶
A 1-sentence description of what your Python package does.
pypi_username¶
Your Python Package Index account username.
version¶
The starting version number of the package.
Options¶
The following package configuration options set up different features for your project.
- use_pytest
Whether to use pytest.
- add_pyup_badge
Whether to include a pyup badge.
- command_line_interface
Whether to create a console script using Click. Console script entry point will match the project_slug. Options: [‘Click’, ‘Argparse’, ‘No command-line interface’]
- create_author_file
Whether to create an authors file.
- create_conventional_commits_edit_message
Whether to use a commit message that helps you adhere to the Conventional Commits specification.
If you plan to use the create_auto_CHANGELOG feature, this template will help you keep your messages in the correct format for the auto CHANGELOG feature.
Important
If you choose yes, don’t forget to run the following command after initiating git to let git know you are using a custom template.
git config --local commit.template .github/.git-commit-template.txt
- create_auto_CHANGELOG
create_auto_CHANGELOG will use GitHub actions to generate a changelog using a cron job, scheduled daily.
- github_access_token
For new or small repositories, select secrets.GITHUB_TOKEN. This is adequate for most small packages.
For larger repositories, the GITHUB_TOKEN may error on the rate limit when generating the CHANGELOG. If so you will need a PAT so select secrets.CHANGELOG_UPDATE.
After generating your GitHub PAT, ensure you use CHANGELOG_UPDATE as the repository secret name. Be careful not to share the secret or commit it to the repository accidentally.
See Encrypted Secrets for more information on generating secrets and repository security.
- open_source_license
Choose a license. Options:
MIT License,
BSD license,
ISC license,
Apache Software License 2.0,
GNU General Public License v3,
Not open source