Could not read username error.

[portlek]

My github action is giving me the error.

name: CI

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - name: Initiate repository
        uses: s4u/maven-settings-action@v2.1.0
        env:
          MAVEN_READ_URL: ${{ secrets.MAVEN_READ_URL }}
          MAVEN_SERVER_ID: ${{ secrets.MAVEN_SERVER_ID }}
          MAVEN_SERVER_PASSWORD: ${{ secrets.MAVEN_SERVER_PASSWORD }}
          MAVEN_SERVER_USERNAME: ${{ secrets.MAVEN_SERVER_USERNAME }}
        with:
          servers: '[{"id": "%MAVEN_SERVER_ID%", "username": "%MAVEN_SERVER_USERNAME%", "password": "%MAVEN_SERVER_PASSWORD%"}]'
          properties: '[{"myMavenRepo.read": "%MAVEN_READ_URL%"}]'

      - name: Set up JDK 1.8
        uses: actions/setup-java@v1
        with:
          java-version: 1.8

      - name: Checkout repository
        uses: actions/checkout@v2
        with:
          path: main

      - name: Checkout private repository
        uses: actions/checkout@v2
        with:
          repository: MinecraftHouse/Ppom
          token: ${{ secrets.ACCESS_TOKEN }}
          path: ppom

#      - name: Build with Maven
#        run: mvn install -Dgpg.skip=true -B -ntp --file pom.xml --settings /home/runner/.m2/settings.xml

[ericsciple]

Does it fail on forks PRs only?

[ericsciple]

Check the details in issue #221

[portlek]

the error changed;

i have ACCESS_TOKEN token tho

and It's not forks or something like that. it's my repo.

[portlek]

the error changed;

i have ACCESS_TOKEN token tho

and It's not forks or something like that. it's my repo.

the error is same with 2.3.1 version

[ericsciple]

Since the token input isnt printed, it looks like ${{ secrets.ACCESS_TOKEN }} is resolving to empty. Here is where the runner prints the inputs.

Can you verify you have a secret ACCESS_TOKEN on the repo? May need to update it.

It doesn't look specific to checkout. The following workflow would have the same result:

on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - run: |
          if [[ "${{secrets.NO_SUCH_SECRET}}" == "" ]]; then
            echo The secret does not exist
          else
            echo The secret exists
          fi

[portlek]

I add asdadas code into the TEST but it's empty too.

[portlek]

ok i found the bug, it was about repo secrets. I didn't add my secrets into repo secrets, it was in the organization secrets where is here

so i add a repo secret called TEST and it worked fine. but it's annoying for me because my secrets are for my all repositories not just 1 and i have 20+ repositories ;( i need a solution for that...

[ericsciple]

I haven't tried it, but this doc seems to indicate it's possible

let me know if that helps

[portlek]

yea i know it, i add my secrets with following this doc. so checkout is not working with organization secret i think. this situation should proof with other users. in my case, its not working.

[Zethson]

Does this suggest the same problem?

https://github.com/luiskuhn/biomedical_semantic_segmentation/runs/1366466968?check_suite_focus=true

I am confused, since there should be a repository secret set with the required value.

[portlek]

I don't remember what was going on here but I solved my problem with a different way, this issue can close.

[Zethson]

@portlek Well, please keep it open for me :)

[brpaz]

I am getting the same error here.

The strange part is that I have two workflows in the same project and only one of them fails. The checkout code is the same.

[munibrahman]

Facing same issue, could be related to switching github accounts?

I was using account A before but now I am using account B.

[GiriRaj249]

I don't remember what was going on here but I solved my problem with a different way, this issue can close.

how did you get it solved ? can you explain it? i am getting same problem with my organization workflow