Skip to content

Update workflow to merge rel-10.2 with rel-10.1#24931

Merged
MansurBesleney merged 1 commit intorel-10.1from
skoc10-patch-3
Feb 24, 2026
Merged

Update workflow to merge rel-10.2 with rel-10.1#24931
MansurBesleney merged 1 commit intorel-10.1from
skoc10-patch-3

Conversation

@skoc10
Copy link
Contributor

@skoc10 skoc10 commented Feb 24, 2026

No description provided.

@MansurBesleney MansurBesleney merged commit 9bd2f63 into rel-10.1 Feb 24, 2026
4 checks passed
@MansurBesleney MansurBesleney deleted the skoc10-patch-3 branch February 24, 2026 07:54
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the GitHub Actions workflow to merge the rel-10.2 branch with rel-10.1 instead of merging the dev branch with rel-10.1. This appears to be a standard update to the automated branch promotion workflow as the project transitions between release versions.

Changes:

  • Updated workflow name, job name, and descriptions from "dev" to "rel-10.2"
  • Changed the source branch reference from "dev" to "rel-10.2"
  • Updated PR title and body text to reflect the new source branch
Comments suppressed due to low confidence (1)

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

  • The workflow trigger should be updated to trigger on pushes to 'rel-10.2' instead of 'rel-10.1'. The workflow is intended to merge rel-10.2 into rel-10.1, so it should trigger when the source branch (rel-10.2) is updated, not when the target branch (rel-10.1) is updated. This would be consistent with standard CI/CD practices where automated merge workflows trigger on changes to the source branch.
    branches:
      - rel-10.1

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants