MicrosoftDocs / azure-docs-sdk-node

Azure for JavaScript and Node.js developers documentation on docs.microsoft.com.
https://docs.microsoft.com/en-us/javascript/azure/
Creative Commons Attribution 4.0 International
86 stars 186 forks source link

update product name #1485

Closed dcurwin closed 1 year ago

dcurwin commented 1 year ago

cc: @VSC-Service-Account

dcurwin commented 1 year ago

sign-off

learn-build-service-prod[bot] commented 1 year ago

Learn Build status updates of commit d6e4ac7:

:white_check_mark: Validation status: passed

File Status Preview URL Details
preview-packages/docs-ref-autogen/@azure/arm-securityinsight/McasDataConnector.yml :white_check_mark:Succeeded View (azure-node-preview)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

dcurwin commented 1 year ago

sign-off

dcurwin commented 1 year ago

@xirzec - Can you help get this published?

dcurwin commented 1 year ago

do we have to re-release the package in order to do so?

@xirzec - I have no information about that. This isn't my repo. I'm just responsible for the documentation for Defender for Cloud Apps, and want to make sure the right term is used.

xirzec commented 1 year ago

@xirzec - I have no information about that. This isn't my repo. I'm just responsible for the documentation for Defender for Cloud Apps, and want to make sure the right term is used.

Perhaps @diberry can remind me about the flow to get this published.

diberry commented 1 year ago

Adding @mcleanbyron.

diberry commented 1 year ago

@xirzec My understanding is that this repo is owned by the Azure SDK team, not the Skilling org.

xirzec commented 1 year ago

@xirzec My understanding is that this repo is owned by the Azure SDK team, not the Skilling org.

Oh wow, that's news to me. According to the internal tooling this repo is owned by @martinekuan and @barbkess -- not sure if we have some side agreement to own it, @kurtzeborn does EngSys own this repo? 😄

diberry commented 1 year ago

@xirzec I could be wrong. Perhaps an email thread with a link to the internal tooling? This repo should have a codeowners file at a minimum.