Skip to content

Conversation

@hgreebe
Copy link
Contributor

@hgreebe hgreebe commented Feb 20, 2025

Description of changes

  • Describe what you're changing and why you're doing these changes.

Tests

  • Describe the automated and/or manual tests executed to validate the patch.
  • Describe the added/modified tests.

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

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.

@hgreebe hgreebe force-pushed the ubuntu-support branch 2 times, most recently from 5b7f0f8 to bc734d1 Compare February 20, 2025 14:37
@hgreebe hgreebe marked this pull request as ready for review February 20, 2025 16:14
@hgreebe hgreebe requested review from a team as code owners February 20, 2025 16:14
@hgreebe hgreebe merged commit bb01db6 into aws:develop Feb 20, 2025
39 of 49 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