-
Notifications
You must be signed in to change notification settings - Fork 0
update dev #158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update dev #158
Conversation
There was a problem hiding this 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 workflow for updating branches and adds a new workflow for auto-deleting branches when a PR is closed.
- Updated the user-update-branch workflow to support multiple target branches via a JSON array and introduced a matrix strategy.
- Modified branch checkout, error messages, and PR creation logic to leverage the new matrix variable.
- Added a new workflow to delete auto-generated branches on pull request closure.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/user-update-branch.yml | Refactored to read multiple target branches using a matrix and updated messages and PR creation conditions. |
| .github/workflows/pr-delete-auto-branches.yml | New workflow to auto-delete branches when a matching pull request is closed. |
|
|
||
| - name: Create PR if conflicts or protected branch | ||
| if: steps.attempt-merge.outputs.merge_status == 'conflict' || steps.push-changes.outputs.push_status == 'failed' | ||
| if: steps.attempt-merge.outcome == 'failure' || steps.attempt-merge.outputs.merge_status == 'conflict' || steps.attempt-merge.outputs.merge_status == 'success' |
Copilot
AI
Apr 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Including 'merge_status' equal to 'success' in the condition for creating a PR could lead to unnecessary PRs when a merge successfully occurs. Consider removing this case so that a PR is created only when the merge fails or there is a conflict.
| if: steps.attempt-merge.outcome == 'failure' || steps.attempt-merge.outputs.merge_status == 'conflict' || steps.attempt-merge.outputs.merge_status == 'success' | |
| if: steps.attempt-merge.outcome == 'failure' || steps.attempt-merge.outputs.merge_status == 'conflict' |
No description provided.