f2beb6369c
|
||
|---|---|---|
| .config | ||
| .devcontainer | ||
| .github | ||
| doc | ||
| eng | ||
| packages | ||
| src | ||
| tools | ||
| .editorconfig | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| LICENSE | ||
| NuGet.Config | ||
| README.md | ||
| SECURITY.md | ||
| global.json | ||
| mgmtci.proj | ||
| package-lock.json | ||
| package.json | ||
README.md
Azure SDK Tools
This repository contains useful tools that the Azure SDK team utilizes across their infrastructure.
Index
| Package or Intent | Path | Description | Status |
|---|---|---|---|
| Check Enforcer [1] | Readme | Manage GitHub check-runs in a mono-repo. | Enabled via GitHub actions |
| doc-warden | Readme | A tool used to enforce readme standards across Azure SDK Repos. | |
| http-fault-injector | Readme | HTTP proxy server for testing HTTP clients during "faults" like "connection closed in middle of body". | |
| Maven Plugin for Snippets | Readme | A Maven plugin that that updates code snippets referenced from javadoc comments. | Not Yet Enabled |
| pixel insertion tool | Readme | A tool used to insert the requests for images served by pixel server. |
Not Yet Enabled |
| pixel-server | Readme | A tiny ASP.NET Core site used to serve a pixel and record impressions. | Not Yet Enabled |
[1] Check Enforcer is located in azure-sdk-actions repo.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
