# Helper scripts

> Shell scripts used by CI workflows and local development for label management, link checking, registry updates, and more.

---

Site [llms.txt](/llms.txt)

---

All scripts live under
[`.github/scripts/`](https://github.com/open-telemetry/opentelemetry.io/tree/main/.github/scripts).

## check-i18n-helper.sh

Validates that localization pages include the required `default_lang_commit`
front matter field. If pages are missing it, the script outputs a fix command:

```sh
npm run fix:i18n:new
```

## pr-approval-labels.sh

Manages PR approval labels based on review state and file ownership. Called by
the [`label-manager` workflow](../ci-workflows/#pr-approval-labels).

**How it works:**

1. Fetches PR data (files changed, latest reviews, current labels) via `gh`.
2. Resolves `docs-approvers` team members from the GitHub org API.
3. Determines required SIG teams by matching changed files against
   [`.github/component-owners.yml`][owners] (parses YAML manually, no `yq`
   dependency).
4. Checks whether each required group has an approving review.
5. Adds or removes labels using tri-state logic (`true`/`false`/`unknown`) to
   avoid changing labels when team membership can't be fetched.

[owners]:
  https://github.com/open-telemetry/opentelemetry.io/blob/main/.github/component-owners.yml

**Required env vars:** `REPO`, `PR`, `GITHUB_TOKEN`.

## update-registry-versions.sh

Auto-updates package versions in `data/registry/*.yml` by querying upstream
registries. Supports: npm, Packagist, RubyGems, Go, NuGet, Hex, Maven.

- In CI (`GITHUB_ACTIONS` set): creates a branch and opens a PR.
- Locally: runs in **dry-run** mode by default. Use `-f` to force real
  execution.

Deduplicates PRs by generating a SHA-1 tag from the update summary.

When versions have changed, the script refreshes the [link cache][] before
committing, since registry updates can add or remove external URLs. A transient
failure during that refresh can leave the bot PR with `CACHE updates committed?`
red even though links pass; comment [`/fix:link-cache`][] on the PR to repair
it. If instead the update introduced a genuinely broken URL, the bot PR arrives
red on the link check itself; fix the URL rather than rerunning the cache fix.

<!-- prettier-ignore-start -->
[`/fix:link-cache`]: /docs/contributing/pull-requests/#fixing-prs-in-github
[link cache]: ../link-checking/#link-cache
<!-- prettier-ignore-end -->