Heroku API Key and Forking
idkjs opened this issue · 2 comments
idkjs commented
TL;DR: Make a note to walkthrough users that they will have to add their Heroku API Key to CircleCI before starting or the first error wont look like the walkthrough. You will get this:
if [ "${CIRCLE_BRANCH}" == "master" ]; then
git push heroku master
heroku run python manage.py deploy
heroku restart
fi
Shell: /bin/bash -eo pipefail
Username for 'https://git.heroku.com': fatal: could not read Username for 'https://git.heroku.com': No such file or directory
Exited with code 128
Adding the key will get you the expected first error.
Also: When forking, make sure to change project name to not conflict on Heroku with the tutorial instance which has the 'cci-demo-walkthrough' namespace occupied.
keybits commented
Thanks for the feedback - I'll be adding this to the README and tutorial soon.
keybits commented
Fixed with: circleci/circleci-docs#1506