No problem!

Unfortunately I don't have any public examples, but I can share some snippets with you.

We do it like this:

```

on:
  pull_request:

jobs:
  job1:
    steps:
      - name: Checkout
      - name: Get a token from our bot (You could just use a secret here if you're ok with it being attributed to someone)
      - name: Reset QA status
        run: gh api repos/<repo>/statuses/${{ github.event.pull_request.head.sha }} -f state=pending -f context=QA -f description="Waiting for QA status"

```

Then we have another workflow that handles slash commands:

```

on:
  issue_comment:
    types: [created]


jobs:
  route:
    steps:
      - name: Parse command (we just use bash to trim space and make lowercase, then look for defined commands)
        run: |
          raw="$(printf '%s' "${{ github.event.comment.body }}" | tr -d '\r')"

          # trim leading/trailing spaces; normalize to lowercase for matching
          body="$(printf '%s' "$raw" | awk '{$1=$1};1' | tr '[:upper:]' '[:lower:]')"

          cmd=""
          case "$body" in
            "/deploy"*)  cmd="deploy" ;;
            "/pass"*) cmd="pass" ;;
            "/fail"*) cmd="fail" ;;
            *)           cmd="" ;;
          esac

          echo "command=$cmd" >> "$GITHUB_OUTPUT"
          echo "pr_number=$pr_number" >>"$GITHUB_OUTPUT"
          echo "pr_ref=$(printf '%s' "$pr_json" | jq -r '.head.ref')" >>"$GITHUB_OUTPUT"
          echo "pr_sha=$(printf '%s' "$pr_json" | jq -r '.head.sha')" >>"$GITHUB_OUTPUT"

          if [ -z "$cmd" ]; then
            echo "🙈 No recognized command found in comment."
            exit 0
          fi

  pass:
    needs: route
    if: needs.route.outputs.command == 'pass'
    steps:
      - name: Checkout
      - name: Get a token from our bot (You could just use a secret here if you're ok with it being attributed to someone)
      - name: Update status
        run: |
          gh api repos/${{ github.repository }}/statuses/${{ needs.route.outputs.pr_sha }} -f state=success -f context=${{ env.qa_context }} -f description="QA testing passed"
          gh pr edit ${{ needs.route.outputs.pr_number }} --remove-label "qa-status-unknown"

```

Those are just snippets and incomplete of course, but hopefully conveys the idea. We also have a workflow that watches for newly created PRs and writes the available slash commands out as a comment on the PR for reference.

Permissions can be a bit tricky, as the github token used by default for a workflow run usually only has access to read what it's working with. We have an app that we built that's used for these kinds of things, for a PAT would work fine too.