Skip to content

Conversation

@Neelabh94
Copy link
Contributor

@Neelabh94 Neelabh94 commented Oct 29, 2025

This PR re-introduces the hook to trigger multi-approver workflow when a new PR is opened and returns to the old workflow as it was before the 13th of October 2025.

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

  • Fork your PR branch from the Toolkit "develop" branch (not main)
  • Test all changes with pre-commit in a local branch #
  • Confirm that "make tests" passes all tests
  • Add or modify unit tests to cover code changes
  • Ensure that unit test coverage remains above 80%
  • Update all applicable documentation
  • Follow Cluster Toolkit Contribution guidelines #

@Neelabh94 Neelabh94 added release-chore To not include into release notes test-enhancement Tests enhancement or coverage improvement labels Oct 29, 2025
@Neelabh94 Neelabh94 marked this pull request as ready for review October 30, 2025 05:13
@Neelabh94 Neelabh94 requested review from a team and samskillman as code owners October 30, 2025 05:13
Copy link
Contributor

@SwarnaBharathiMantena SwarnaBharathiMantena left a comment

Choose a reason for hiding this comment

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

Please test the multi-approvers workflow once the merge is completed.

@Neelabh94 Neelabh94 force-pushed the feature/update-multi-approver-workflow branch from 59adce3 to 6c257b2 Compare October 30, 2025 06:39
@Neelabh94 Neelabh94 force-pushed the feature/update-multi-approver-workflow branch from 6c257b2 to 9c90db2 Compare November 13, 2025 07:01
@Neelabh94 Neelabh94 changed the title Multi-Approvers Workflow Migration fix: Multi-Approvers Workflow Nov 13, 2025
Copy link
Collaborator

@bytetwin bytetwin left a comment

Choose a reason for hiding this comment

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

This change triggers multi approvers only when the event_name is pr_review (refer line 43). Do we need to trigger for event_name = pr ?

@Neelabh94 Neelabh94 force-pushed the feature/update-multi-approver-workflow branch from 2f3f171 to 7b7226f Compare November 13, 2025 10:20
Copy link
Contributor

@SwarnaBharathiMantena SwarnaBharathiMantena left a comment

Choose a reason for hiding this comment

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

LGTM

Note: This will bring back the initial reason why this file was modified, that is the requirement that the PR test for pull request will not automatically run and will need a manual run click.

@Neelabh94 Neelabh94 merged commit 40eee2d into GoogleCloudPlatform:develop Nov 13, 2025
13 of 67 checks passed
@Neelabh94 Neelabh94 deleted the feature/update-multi-approver-workflow branch November 14, 2025 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-chore To not include into release notes test-enhancement Tests enhancement or coverage improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants