Skip to content

👷 Fix Octo release policy #3821

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 4, 2025
Merged

👷 Fix Octo release policy #3821

merged 1 commit into from
Sep 4, 2025

Conversation

amortemousque
Copy link
Collaborator

Motivation

Fix Octo regex release policy

Changes

Test instructions

Checklist

  • Tested locally
  • Tested on staging
  • Added unit tests for this change.
  • Added e2e/integration tests for this change.

@amortemousque amortemousque requested a review from a team as a code owner September 4, 2025 12:10
@amortemousque amortemousque merged commit 67b92ea into main Sep 4, 2025
13 of 18 checks passed
@amortemousque amortemousque deleted the aymeric/fix-octo-release-policy branch September 4, 2025 12:11
@datadog-official Datadog Official
Copy link

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
• Patch Coverage: 100.00%
• Total Coverage: 92.55% (-0.02%)

View detailed report

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: da427df | Docs | Was this helpful? Give us feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@BenoitZugmeyer BenoitZugmeyer BenoitZugmeyer approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@amortemousque @BenoitZugmeyer