Skip to content
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

[Parent issue] Create and add CODEOWNERS linter baseline files #7122

Closed
JimSuplizio opened this issue Oct 12, 2023 · 1 comment
Closed

[Parent issue] Create and add CODEOWNERS linter baseline files #7122

JimSuplizio opened this issue Oct 12, 2023 · 1 comment
Assignees
Labels
CODEOWNERS Linter Anything related to the CODEOWNERS linter

Comments

@JimSuplizio
Copy link
Member

Before creating and enabling the CodeownersLinter pipelines, every repository that this will be enabled for needs to have a baseline file created and checked in. The baseline file will be used to filter errors, allowing the pipeline run and pass in spite of existing errors. This will allow the pipeline to be enabled for CODEOWNERS changes and only report or block a check in if someone is adding brand new errors to a CODEOWNERS files. AKA, it'll allow the existing errors, at least until the baseline errors are fixed, and prevent new errors for being added.

The repositories that require baseline files are
azure-sdk
azure-sdk-tools
azure-sdk-for-android
azure-sdk-for-c
azure-sdk-for-cpp
azure-sdk-for-go
azure-sdk-for-ios
azure-sdk-for-java
azure-sdk-for-js
azure-sdk-for-net
azure-sdk-for-python

@JimSuplizio
Copy link
Member Author

Closing this out, all of the repositories now have their CODEOWNERS linter error baseline files and linter pipelines created and enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CODEOWNERS Linter Anything related to the CODEOWNERS linter
Projects
None yet
Development

No branches or pull requests

1 participant