-
Notifications
You must be signed in to change notification settings - Fork 183
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
/.azure-pipelines/warden.yml
→ /eng/pipelines/doc-warden.yml
#5617
Conversation
.azure-pipelines/warden.yml
→ eng/pipelines/doc-warden.yml
@weshaggard the warden pipeline has all its triggers disabled via ADO UI and last run was in Dec 9, 2021, over 14 months ago. There also doesn't seem to be much activity in the packages/python-packages/doc-warden. @scbedd @heaths @chidozieononiwu do you folks know if doc warden is still in use? I guess the pipeline is not in use recently as there weren't any code changes, but the package is in fact being used? |
.azure-pipelines/warden.yml
→ eng/pipelines/doc-warden.yml
/.azure-pipelines/warden.yml
→ /eng/pipelines/doc-warden.yml
I didn't realize it wasn't running, but I don't know why it was turned off. I know it found some valid issues. |
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.
Looks good. Be sure to update the pipeline to point to the new location.
@konrad-jamrozik it is still in use for most of our language repos today. We have plans to retire it and move to a more generic MD linter tool in the future but that work is still on the backlog. See #1896 |
/check-enforcer override |
PR merged & I have updated the pipeline. |
Contributes to:
Once this PR is merged, I will update the relevant pipeline to point to the new location of its definition file:
https://dev.azure.com/azure-sdk/internal/_build?definitionId=106