Skip to content

fix(query): serve service drill-downs from the trace index #559

fix(query): serve service drill-downs from the trace index

fix(query): serve service drill-downs from the trace index #559

Workflow file for this run

name: CLA

Check warning on line 1 in .github/workflows/cla.yml

View workflow run for this annotation

GitHub Actions / CLA

Workflow execution policy warning (evaluate mode)

On December 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
on:
issue_comment:
types: [created]
pull_request_target:
types: [opened, synchronize, reopened]
permissions:
actions: write
# write, not read: the action commits each signature to the branch below.
contents: write
pull-requests: write
statuses: write
jobs:
cla:
name: Check CLA
runs-on: ubuntu-24.04
# Only react to the signature sentence, or to pull request events. Note this
# workflow never checks out pull request code: `pull_request_target` runs
# with a writable token in the base repository context, so running a
# contributor's code here would hand them that token.
if: >-
github.event_name == 'pull_request_target' ||
(github.event.issue.pull_request != null &&
github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA')
steps:
- uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
path-to-document: https://github.com/labstack/fanout/blob/main/CLA.md
path-to-signatures: signatures.json
# Signatures live on their own branch. Storing them on main would put
# a bot commit into the release history and trigger a CI run plus an
# image publish every time somebody signs.
branch: cla-signatures
allowlist: vishr,dependabot[bot]