You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ShivangiReja opened this issue
Jan 15, 2021
· 5 comments
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.CodeGenIssues that relate to code generationEngSysThis issue is impacting the engineering system.
Enable track-2 sdk automation for all the services in the specs repo. If the service is new or the sdk doesn't exists in azure-sdk-for-net repo, it won't affect anything. It will only generate code for existing swagger updates.
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jan 15, 2021
ShivangiReja
added
Client
This issue points to a problem in the data-plane of the library.
CodeGen
Issues that relate to code generation
EngSys
This issue is impacting the engineering system.
labels
Jan 15, 2021
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jan 15, 2021
Hi @ShivangiReja. There hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by removing the no-recent-activity label. Otherwise, we'll close this out in 7 days.
Hi @ShivangiReja. There was a mistake and this issue was unintentionally flagged as a stale pull request. The label has been removed and the issue will remain active; no action is needed on your part. Apologies for the inconvenience.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
ClientThis issue points to a problem in the data-plane of the library.CodeGenIssues that relate to code generationEngSysThis issue is impacting the engineering system.
Enable track-2 sdk automation for all the services in the specs repo. If the service is new or the sdk doesn't exists in azure-sdk-for-net repo, it won't affect anything. It will only generate code for existing swagger updates.
For more details: #15585
The text was updated successfully, but these errors were encountered: