Update workflow to merge rel-10.4 with rel-10.3

[skoc10]

No description provided.

[Copilot]

Pull request overview

Updates the GitHub Actions automation that opens a promotion PR, switching it from promoting dev into rel-10.3 to promoting rel-10.4 into rel-10.3.

Changes:

• Renamed the workflow and job to reflect rel-10.4 → rel-10.3.
• Updated the checkout ref from dev to rel-10.4.
• Updated the generated PR title/body to reference rel-10.4.

Comments suppressed due to low confidence (2)

.github/workflows/auto-pr.yml:5

• The workflow name/title now indicates it merges rel-10.4 into rel-10.3, but the workflow is still triggered only on pushes to rel-10.3. If the intent is to promote changes from rel-10.4 down to rel-10.3, this should likely run on pushes to rel-10.4 (or on a schedule / manual dispatch) so new rel-10.4 commits actually generate a PR.

name: Merge branch rel-10.4 with rel-10.3
on:
  push:
    branches:
      - rel-10.3

.github/workflows/auto-pr.yml:22

• With ref: rel-10.4 followed by git reset --hard rel-10.3, the working tree ends up at rel-10.3 without ever merging rel-10.4 into it. As a result, create-pull-request will likely see no changes and skip creating a PR (or create an empty PR). Add an explicit merge step (e.g., merge origin/rel-10.4 into the promotion branch based on rel-10.3), or remove the reset and configure the action to open a PR from rel-10.4 to rel-10.3 using the base input.

          ref: rel-10.4
      - name: Reset promotion branch
        run: |
          git fetch origin rel-10.3:rel-10.3
          git reset --hard rel-10.3

[Copilot]

Grammar: the PR body is missing “is” ("This PR is generated automatically …"). Consider fixing the sentence to improve clarity in the generated PR description.

Suggested change

	body: This PR generated automatically to merge rel-10.4 with rel-10.3. Please review the changed files before merging to prevent any errors that may occur.
	body: This PR is generated automatically to merge rel-10.4 with rel-10.3. Please review the changed files before merging to prevent any errors that may occur.