Skip to content

Conversation

@kei-gnu
Copy link

@kei-gnu kei-gnu commented Nov 24, 2025

What does the PR do?

Add missing space after # in comment for consistency with coding style conventions.

Checklist

  • I have read the Contribution guidelines and signed the Contributor License
    Agreement
  • PR title reflects the change and is of format <commit_type>: <Title>
  • Changes are described in the pull request.
  • Related issues are referenced.
  • Populated github labels field
  • Added test plan and verified test passes.
  • Verified that the PR passes existing CI.
  • I ran pre-commit locally (pre-commit install, pre-commit run --all)
  • Verified copyright is correct on all changed files.
  • Added succinct git squash message before merging ref.
  • All template sections are filled out.
  • Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

  • build
  • ci
  • docs
  • feat
  • fix
  • perf
  • refactor
  • revert
  • style
  • test

Related PRs:

Where should the reviewer start?

Test plan:

Caveats:

Background

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

  • closes GitHub issue: #xxx

@kei-gnu kei-gnu changed the title fix:comment formatting in docker/sagemaker/serve fix: comment formatting in docker/sagemaker/serve Nov 24, 2025
@kei-gnu kei-gnu marked this pull request as ready for review November 24, 2025 15:31
@kei-gnu kei-gnu changed the title fix: comment formatting in docker/sagemaker/serve fix: comment in docker/sagemaker/serve Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant