Skip to content

Add block_failure telemetry for Tomcat blocking enforcement failures #1130

Add block_failure telemetry for Tomcat blocking enforcement failures

Add block_failure telemetry for Tomcat blocking enforcement failures #1130

# How to configure:

Check warning on line 1 in .github/workflows/team-freeze-guard.yaml

View workflow run for this annotation

GitHub Actions / Team freeze guard

Workflow execution policy warning (evaluate mode)

On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
#
# When no team is frozen, set `frozen-teams` to an empty string:
# frozen-teams: ""
#
# When one or more teams are frozen, add them one per line with the @DataDog prefix:
#
# frozen-teams: |
# @DataDog/team-a
# @DataDog/team-b
name: Team freeze guard
on:
pull_request_target:
types:
- opened
- reopened
- synchronize
- labeled
- unlabeled
- ready_for_review
permissions:
id-token: write
contents: read
jobs:
team-freeze-guard:
name: Team freeze guard
runs-on: ubuntu-latest
steps:
- uses: DataDog/team-freeze-guard@e4ff51a72cac229b238e5a302af0d3d955ae5b54 # v0.0.4
with:
bypass-labels: |
comp: testing
comp: tooling
tag: flaky test
tag: flaky test/disabled
frozen-teams: ""