Skip to content

Update branch reference in auto-pr workflow#25219

Merged
EngincanV merged 1 commit into
rel-10.3from
maliming-patch-3
Apr 8, 2026
Merged

Update branch reference in auto-pr workflow#25219
EngincanV merged 1 commit into
rel-10.3from
maliming-patch-3

Conversation

@maliming

@maliming maliming commented Apr 8, 2026

Copy link
Copy Markdown
Member

Resolve merge conflicts in the PR.

Change the branch reference from 'rel-10.3' to 'dev' in the workflow.
@EngincanV EngincanV merged commit c827a29 into rel-10.3 Apr 8, 2026
4 checks passed
@EngincanV EngincanV deleted the maliming-patch-3 branch April 8, 2026 06:28

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the auto PR GitHub Actions workflow to change which branch is checked out when generating automated merge PRs.

Changes:

  • Change actions/checkout ref from rel-10.3 to dev in .github/workflows/auto-pr.yml.
Comments suppressed due to low confidence (1)

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

  • The branch refs in this workflow look internally inconsistent: it checks out dev but then immediately hard-resets the working tree to rel-10.3, which effectively discards the checkout and makes it unclear what content the PR will be created from. If the intent is "merge dev into rel-10.3" (per workflow name/title/body), the usual approach is to check out the base branch (rel-10.3) and then reset to the source branch (dev) (or explicitly set base: rel-10.3 in create-pull-request and ensure the git reset targets dev). Please align actions/checkout ref, the git fetch/git reset targets, and (if needed) the on.push.branches trigger so the PR is generated in the intended direction.
      - uses: actions/checkout@v2
        with:
          ref: dev
      - name: Reset promotion branch
        run: |
          git fetch origin rel-10.3:rel-10.3
          git reset --hard rel-10.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants