Skip to content

Fix "fatal: could not read Username..."#132

Merged
TimHess merged 2 commits intomainfrom
keep-alive_credentials
Apr 7, 2026
Merged

Fix "fatal: could not read Username..."#132
TimHess merged 2 commits intomainfrom
keep-alive_credentials

Conversation

@TimHess
Copy link
Copy Markdown
Member

@TimHess TimHess commented Apr 2, 2026

The scheduled keep-alive job failed on it's first run with:

fatal: could not read Username for 'https://github.com/': No such device or address
Error: Process completed with exit code 128.

This happens when the job tries to run git push origin "$branch_name", effectively without credentials, because persist-credentials is set to false and we aren't completely configuring git another way.

We should be able to fix this by either:

  • removing this:
    with:
      persist-credentials: false
    
  • adding this:
    git remote set-url origin "https://x-access-token:${GH_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
    

@TimHess TimHess requested a review from bart-vmware April 2, 2026 15:57
@TimHess TimHess merged commit 808c6c5 into main Apr 7, 2026
8 checks passed
@TimHess TimHess deleted the keep-alive_credentials branch April 7, 2026 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants