Skip to content

Conversation

@kshitij-microsoft
Copy link
Member

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-sdk
Copy link
Collaborator

azure-sdk commented Dec 12, 2024

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-ai-ml

@kshitij-microsoft kshitij-microsoft marked this pull request as ready for review January 2, 2025 06:40
@kshitij-microsoft kshitij-microsoft changed the title YAML signing [DRAFT] YAML signing Jan 2, 2025
@kshitij-microsoft kshitij-microsoft force-pushed the feature/yamlSigning branch 4 times, most recently from de4e8cd to 7a0b159 Compare January 2, 2025 16:10
@kshitij-microsoft kshitij-microsoft merged commit 596b2c0 into Azure:main Jan 2, 2025
21 checks passed
kshitij-microsoft added a commit to kshitij-microsoft/azure-sdk-for-python that referenced this pull request Jan 2, 2025
* first draft : YAML signing

* YAML signing

* component ops adding prepare for sign

* resolving comments

* fixing pylint and black
achauhan-scc pushed a commit that referenced this pull request Jan 3, 2025
* first draft : YAML signing

* YAML signing

* component ops adding prepare for sign

* resolving comments

* fixing pylint and black
singankit pushed a commit that referenced this pull request Jan 14, 2025
* first draft : YAML signing

* YAML signing

* component ops adding prepare for sign

* resolving comments

* fixing pylint and black
l0lawrence pushed a commit to l0lawrence/azure-sdk-for-python that referenced this pull request Feb 19, 2025
* first draft : YAML signing

* YAML signing

* component ops adding prepare for sign

* resolving comments

* fixing pylint and black
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.

3 participants