ci: deploy jobs in `push.yml` are skipped because they only run on `refs/heads/main`

[fallintoplace]

Description

The deploy jobs in .github/workflows/push.yml currently only run when:

if: github.ref == 'refs/heads/main'

However, the repository's current default branch is 16.x.x, and there is no main branch in the repository.

That means the deploy jobs appear to be unreachable on the active branches that currently carry this workflow.

Current workflow

on: push

jobs:
  deploy-to-npm-branch:
    needs: ci
    if: github.ref == 'refs/heads/main'
    ...

  deploy-to-deno-branch:
    needs: ci
    if: github.ref == 'refs/heads/main'
    ...

Evidence

• gh repo view graphql/graphql-js --json defaultBranchRef reports the default branch as 16.x.x.
• git branch -r in a fresh clone does not show origin/main.
• A recent push.yml run on the default branch (16.x.x) completed CI and artifact build jobs, but both deploy jobs were skipped:
  • workflow run: Push run 26132380585
  • head branch: 16.x.x
  • skipped jobs: Deploy to 'npm' branch and Deploy to 'deno' branch

Possible fix

Update the branch condition to match the branch that should actually trigger these deployments, or otherwise derive it from the current release workflow.

Follow-up

If the branch gate is updated, the commit_message values in the same workflow may also need attention because they currently reference github.event.workflow_run.head_sha, even though this workflow runs on push events.

[yaacovCR]

That tracks. It looks like we have not been publishing to npm/deno branches since we renamed main to next (and then later rebased next into 16.x.x to yield17.x.x more than a year ago.

And it looks like since the creation of this job in #3488 => the commit_message values have been elided. It seems like those interested in the bleeding edge have sufficed themselves with our alpha releases.

We should fix this.