Skip to content
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

Port auto-pr workflow to branch 3 #1209

Merged
merged 1 commit into from
Oct 23, 2023
Merged

Port auto-pr workflow to branch 3 #1209

merged 1 commit into from
Oct 23, 2023

Conversation

komamitsu
Copy link
Contributor

@komamitsu komamitsu commented Oct 20, 2023

Description

We allowed Auto PR workflow to work with release/support branches. But it didn't work since the destination branches don't have the workflow.

Related issues and/or PRs

Changes made

This PR copies the latest Auto PR workflow file to the release/support branch.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

  • I have commented my code, particularly in hard-to-understand areas.
  • I have updated the documentation to reflect the changes.
  • Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
  • Tests (unit, integration, etc.) have been added for the changes.
  • My changes generate no new warnings.
  • Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

This change is to update the existing old workflow. The diff is same as the diff between 3.10 and master. As for other release/support branches that don't have the workflow file, I'll create another PR to create it.

Release notes

N/A

Copy link
Collaborator

@brfrn169 brfrn169 left a comment

Choose a reason for hiding this comment

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

LGTM! Thank you!

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

Successfully merging this pull request may close these issues.

2 participants