chore(deps): try another approach for... (#2018)

chore(deps): try another approach for getting GITHUB_TOKEN into the yarn lock regen

Signed-off-by: Nick Boldt <[email protected]>

.github/actions/yarn-lock/action.yaml

@@ -17,6 +17,8 @@ runs:
           git config --global user.email [email protected]
           git config --global pull.rebase true 
           git config --global push.default matching
+          # workaround for "fatal: could not read Username for 'https://github.com'"
+          git config remote.origin.url "https://${GITHUB_TOKEN}:[email protected]/janus-idp/backstage-plugins.git"
 
           git stash || true
           CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)

.github/workflows/push.yaml

@@ -32,8 +32,12 @@ jobs:
           app-id: ${{ vars.JANUS_IDP_GITHUB_APP_ID }}
           private-key: ${{ secrets.JANUS_IDP_GITHUB_APP_PRIVATE_KEY }}
 
-      - name: Setup git credentials
-        run: git config --global url.https://${{ steps.generate-token.outputs.token }}@github.com/.insteadOf https://github.com/
+      # - name: Setup git credentials
+      #   run: |
+      #     git config --global url.https://rhdh-bot:${{ steps.generate-token.outputs.token }}@github.com/.insteadOf https://github.com/
+      #     # Fix for Could not read Username / No such device or address :: https://github.com/github/hub/issues/1644
+      #     # git config --global hub.protocol https
+      #     # git remote set-url origin 'https://\$GITHUB_TOKEN:x-oauth-basic@'
 
       - name: Regen yarn.lock
         uses: ./.github/actions/yarn-lock