Skip to content

Adds accepted reasons for archiving signal #2162

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

Merged

Conversation

api-clients-generation-pipeline[bot]
Copy link
Contributor

@api-clients-generation-pipeline api-clients-generation-pipeline bot requested a review from a team as a code owner September 16, 2024 18:20
@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/3116 branch 7 times, most recently from 78d5103 to cb7eb29 Compare September 20, 2024 13:54
@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/3116 branch from cb7eb29 to ac062d3 Compare September 20, 2024 14:05
@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/3116 branch from ac062d3 to 218ad04 Compare November 7, 2024 20:44
@api-clients-generation-pipeline api-clients-generation-pipeline bot merged commit e31f308 into master Nov 7, 2024
13 checks passed
@api-clients-generation-pipeline api-clients-generation-pipeline bot deleted the datadog-api-spec/generated/3116 branch November 7, 2024 21:27
github-actions bot pushed a commit that referenced this pull request Nov 7, 2024
* Regenerate client from commit efa118f1 of spec repo

* pre-commit fixes

---------

Co-authored-by: ci.datadog-api-spec <[email protected]> e31f308
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants