Skip to content

[2/2] Moving repo specific nuget package metadata to working branch#4366

Closed
hovsepm wants to merge 1 commit intoAzure:NetSdkBuildfrom
hovsepm:NetSdkBuild
Closed

[2/2] Moving repo specific nuget package metadata to working branch#4366
hovsepm wants to merge 1 commit intoAzure:NetSdkBuildfrom
hovsepm:NetSdkBuild

Conversation

@hovsepm
Copy link
Copy Markdown
Contributor

@hovsepm hovsepm commented May 24, 2018

Description


This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • 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.

SDK Generation Guidelines

  • 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.
  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
  • The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@hovsepm hovsepm requested a review from shahabhijeet May 24, 2018 22:17
@shahabhijeet
Copy link
Copy Markdown
Contributor

@hovsepm as discussed offline, you don't need these changes in these branches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants