Update hardcoded branch name in workflow files when default branch is renamed

[wrigjl]

Problem

All three workflow files hardcode ReduxAPI_GUI as the branch name in their on: trigger filters:

• .github/workflows/code-analysis.yml — push and pull_request filters (lines 17–18)
• .github/workflows/main.yml — pull_request filter
• .github/workflows/publish.yml — push filter

If the default branch is ever renamed, these workflows will silently stop triggering on push and pull_request events to the new default branch.

Fix

Replace the hardcoded ReduxAPI_GUI with GitHub's $default-branch token in each branches: filter:

on:
  push:
    branches: [ $default-branch ]
  pull_request:
    branches: [ $default-branch ]

$default-branch is a GitHub-recognized token in branches: filters that resolves to whatever the repository's current default branch is set to. This makes the workflows resilient to future branch renames without any further changes.

Why now

The Redux project is considering renaming default branches across its repositories. Updating the workflows first (or alongside the rename) avoids a window where CI stops running on the new default branch.

See also: ReduxISU/Redux#295 for the same change in the backend repo.

[wrigjl]

Update: $default-branch only works in GitHub workflow template files, not in actual .github/workflows/ files — the token is substituted at template-instantiation time, not at workflow-run time. There is no runtime expression available in branches: filters.

The branch name must be hardcoded. When the default branch is renamed, the following three files need a one-line update each:

• .github/workflows/code-analysis.yml — branches: [ "<new-name>" ] (two occurrences: push and pull_request)
• .github/workflows/main.yml — branches: - <new-name>
• .github/workflows/publish.yml — branches: - <new-name>

Keeping this issue open as a reminder to make those updates as part of the rename procedure.