-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs onboarding v2 #36383
Docs onboarding v2 #36383
Conversation
…gs.ps1 and should not publish docs.
… on local machine are clean, it's OK if files aren't present to clean up.
…e-Settings.ps1 and should not publish docs." This reverts commit d383cad.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per our discussion, I'm good with these changes.
@@ -9,6 +9,7 @@ $GithubUri = "https://github.com/Azure/azure-sdk-for-java" | |||
$PackageRepositoryUri = "https://repo1.maven.org/maven2" | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When do you plan to use the new script you are adding to common in Azure/azure-sdk-tools#6632?
/check-enforcer override |
This PR culminates several iterations of cleanup in the Java Docs repo and handles some strange behavior seen along the way.
Note: There's also a cleanup PR to cleanup older language specific items.
This does not directly support
legacy
onboarding yet as we'll need to migrate thelegacy
moniker toarchive
first and then onboard some deprecated packages intolegacy
.Part of this cleanup includes setting
skipPublishDocMs
for packages that are already excluded from docs onboarding. #36385