0

I've already attempted to ask about this on the repo itself with no luck so far.

I've created a fairly simple workflow based on this SO answer to retrieve a forgotten secret:

name: Show Me the S3cr3tz
on: [push]

jobs:
  debug:
    name: Debug
    runs-on: ubuntu-latest

    steps:
      - name: Check out code
        uses: actions/checkout@v2

      - name: Set up secret file
        env:
          MY_SECRET: ${{ secrets.MY_SECRET }}
        run: |
          echo $MY_SECRET >> secrets.txt

      - name: Run tmate
        uses: mxschmitt/action-tmate@v3

However, I can never see the tmate link because it is cancelled automatically and immediately after leaving the queue:

This check was cancelled

What am I doing wrong?

Sturm
  • 689
  • 2
  • 23
  • 52
  • As a side note, if your secret contains special characters, it might undergo parameter expansion – use `printf '%s\n' "$MY_SECRET"` instead of `echo $MY_SECRET`. – Benjamin W. May 19 '21 at 13:14
  • This seems like a GitHub Actions issue, not an issue with your syntax. I just tested your exact code in my repo and I get a tmate session just fine. Have you tried running it more than once? – DannyB May 20 '21 at 11:10
  • @DannyB I wouldn't have posted here if I hadn't tried it more than once. That's why there's a "#5" next to the name of the workflow in that screenshot. However, you are absolutely correct; Github Actions must have been having some hiccups that day because it's now working perfectly. I don't think there's any way I can retract the question, so feel free to write an answer stating that Github Actions was having a bad day and I'll choose it as the correct answer. Otherwise, I'll just create a quick answer myself. Thanks! – Sturm May 20 '21 at 13:47

1 Answers1

1

This is probably related to the recent GitHub Actions outage.

The workflow YAML syntax is valid, and confirmed to be working.

DannyB
  • 12,810
  • 5
  • 55
  • 65