Skip to content

Conversation

@hanwen-cluster
Copy link
Contributor

@hanwen-cluster hanwen-cluster commented May 9, 2025

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@hanwen-cluster hanwen-cluster requested review from a team as code owners May 9, 2025 14:00
@hanwen-cluster hanwen-cluster force-pushed the developmay8fix branch 5 times, most recently from 3085668 to 01dab11 Compare May 9, 2025 14:46
@hanwen-cluster hanwen-cluster changed the title Fix Github check Fix Github check by pinning the docker image May 9, 2025
@hanwen-cluster hanwen-cluster merged commit a8c94de into aws:develop May 9, 2025
30 of 43 checks passed
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