New PR check workflow #5460
Merged
New PR check workflow #5460
+63
−16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mollyheamazon
approved these changes
Jan 6, 2026
rsareddy0329
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Currently, PR checks are only triggered on any sub-modules that are directly affected. However, changes made to submodules like sagemaker-core or sagemaker-train may still affect parent modules like sagemaker-serve and sagemaker-mlops. This new workflow will trigger PR checks not only for submodules that are directly changed but also any submodules that depend on the changed set of submodules. For example, a change in sagemaker-train will now trigger PR checks in sagemaker-train, sagemaker-serve, and sagemaker-mlops. This new workflow has been rigorously tested.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.