-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying to *** #10
Comments
I would get rid of the "buildpack", "branch", "dontuseforce" and "appdir" variables in your action since you aren't using them. Your yaml file should look something like: name: CI
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Install dependencies
run: yarn install
- name: Test project
run: yarn test
- name: Build project
run: yarn build
- name: Deploy to Heroku
uses: AkhileshNS/heroku-deploy@master
with:
heroku_api_key: ${{ secrets.HEROKU_API_KEY }}
heroku_email: ${{ secrets.HEROKU_EMAIL }}
heroku_app_name: ${{ secrets.HEROKU_APP_NAME }} Also in your output *** is just github actions hiding secrets from being printed in the logs. So its likely the *** is actually just the value of secrets.HEROKU_APP_NAME. Also never leave a value like |
Thank you for the prompt response, you're great, it was that. Also thanks for helping me understand the *** thing. I'll keep the rest of your advice in mind, have a great day :) |
This may be an issue on how I'm doing things, but I'm not able to deploy to my project and the log says I'm trying to push to *** instead.
Here's the full output:
Here's my yml file:
I added the secrets to my config a couple times already to make sure I wrote the correct values, seems like at least API_KEY is working correctly because the action is able to login.
I don't know what else to try, I tried adding the app name to the yml or adding it as a secret to no avail.
I'm learning Github Actions and I'm frustrated because I can't find a way out of this fairly easy problem.
Do you have an idea on how could I fix this?
The text was updated successfully, but these errors were encountered: