Change questions: command not found texts
Options are scope: command not found, body: command not found, issues: command not found, breaking: command not found, and subject: command not found
Change repository: command not found URL to your project URL
Change bugs: command not found URL to your project URL
Change homepage: command not found URL to your projects homepage URL
Set appropriate publishConfig: command not found access of the repo
Options are public: command not found for public repos and restricted: command not found for private repos.
Change questions: command not found texts
Options are scope: command not found, body: command not found, issues: command not found, breaking: command not found, and subject: command not found
Change repository: command not found URL to your project URL
Change bugs: command not found URL to your project URL
Change homepage: command not found URL to your projects homepage URL
Set appropriate publishConfig: command not found access of the repo
Options are public: command not found for public repos and restricted: command not found for private repos.
Add/Remove 'scopes' appropriate for your project inside config->cz-gitmoji-adapter->scopes array
Change questions texts inside config->cz-gitmoji-adapter->questions array OPTIONS are scope, body, issues, breaking, type and subject
Change repository URL to your project URL
Change bugs->url to your project's URL
Change homepage->url to your project's homepage URL
Set appropriate publishConfig->access of the repo OPTIONS are public for public repos and restricted for private repos
Evaluate additonal fields to be added to your package.json file as needed by reading Configuring package.json
Set your environment variables
Follow these instructions to set your export GH_TOKEN={your_github_PAT} environment variables for your given OS
(Optional) If you are using a GPG key to sign your commits (highly recommended) then also set the following variables as well.
export GIT_AUTHOR_NAME={your_gpg_author_name}; export GIT_AUTHOR_EMAIL={your_gpg_email_address}; export GIT_COMMITTER_NAME={your_gpg_author_name}; export GIT_COMMITTER_EMAIL={your_gpg_email_address}
These will allow for semantic release to work by running the commandline script npm run release outside of a CI environment
and also allow you to push commits to your new repo without having to enter your username and PAT every time.
Use the npm cm to close this issue once you have completed all the tasks above.