This repository contains reusable GitHub Actions components shared across multiple OpenTelemetry repositories.
See CONTRIBUTING.md for how to propose a new shared workflow or use an existing one.
| Name | Description | How to use |
|---|---|---|
| Changelog | Reusable workflow that enforces the chloggen-style changelog process: blocks direct CHANGELOG*.md edits, requires a .chloggen/*.yaml entry, validates it, and link-checks its rendered preview. |
Call via uses: from your repo's pull_request workflow. See the Changelog README for the snippet. |
| First-time contributor | Reusable workflow that welcomes first-time contributors on pull_request_target: opened: applies a label and posts a customizable welcome comment. |
Call via uses: from your repo's pull_request_target workflow. See the First-time contributor README for the snippet. |
| FOSSA | Reusable workflow that runs FOSSA license and dependency scanning for the OpenTelemetry team. | Call via uses: from your repo's workflow. See the FOSSA README for the snippet. |
| GitHub Actions queue data | Centrally collects per-job queue timing data for active public repositories in the OpenTelemetry organization. | Configure the read-only GitHub App described in the GitHub Actions queue data README. |
| OSSF Scorecard | Reusable workflow that runs OpenSSF Scorecard, publishes the full result for the badge, and uploads a subset of its checks to code scanning. | Call via uses: from your repo's workflow. See the OSSF Scorecard README for the snippet. |
| Pull Request Dashboard | Centrally-executed workflow that builds a per-repository pull request triage dashboard (issue body, status, Slack notifications) for opted-in repositories. | Add your repository to repositories.json and follow the setup in the workflow's README. |
| Survey on merged PR | Reusable workflow that posts a survey link to a merged PR when the author is a new contributor. | Call via uses: from your repo's pull_request_target: closed workflow. See the Survey on merged PR README for the snippet. |
| Workflow failure issue | Reusable workflow that tracks a workflow's pass/fail state by opening, commenting on, and closing a GitHub issue in the calling repository — useful for scheduled workflows whose failure notifications otherwise reach only a single user. | Call via uses: from a final if: always() job in the workflow you want to monitor. See the Workflow failure issue README for the snippet. |
| Zizmor | Static analysis of GitHub Actions workflows for security issues using zizmor. | Call via uses: from your repo's workflow. See the Zizmor README for the snippet. |
- Adriel Perkins, Grainger
- Marylia Gutierrez, Grafana Labs
- Pablo Baeyens, Datadog
- Trask Stalnaker, Microsoft
For more information about the maintainer role, see the community repository.
- Alex Boten, Grafana Labs
- Piotr Kiełkowicz, Splunk
For more information about the approver role, see the community repository.