heroku-deploy icon indicating copy to clipboard operation
heroku-deploy copied to clipboard

[BUG] could not read Username for 'https://github.com'

Open GrassBlock1 opened this issue 3 years ago • 3 comments

First of all thanks for creating this awesome github action! I am a bit new to this ecosystem so forgive me :bow:

I have it used with a private repo , but when I pushed to master , I got error and saw these logs:

fatal: could not read Username for 'https://github.com/': No such device or address
Error: Error: Command failed: git fetch --prune --unshallow
fatal: could not read Username for 'https://github.com/': No such device or address

And here is my workflow file:

# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the workflow will run
on:
  # Triggers the workflow on push or pull request events but only for the master branch
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v2
        with:
          persist-credentials: false
          submodules: true
      - name: Deploy to Heroku
        uses: akhileshns/[email protected]
        with:
          heroku_api_key: ${{secrets.HEROKU_API_KEY}}
          heroku_app_name: "grassblogx" #Must be unique in Heroku
          heroku_email: "(email is hidden but it's right)"

Maybe caused by using HTTP access? I don't know really, any solutions?

GrassBlock1 avatar Feb 24 '22 01:02 GrassBlock1

same issue here

lazyseals avatar Feb 28 '22 12:02 lazyseals

Problem Still exists, just a operation mistake.

GrassBlock1 avatar Mar 12 '22 07:03 GrassBlock1

This is because the deployment involves git, and you've got persist-credentials set to false in actions/checkout.

G-Rath avatar Dec 02 '22 00:12 G-Rath