Home · Extensions · .trigger

`.trigger`

2 claimants 0 primary 2 secondary secondary-only

SWH popularity

Distinct files in the full Software Heritage archive (2026-06-04 export), dated by first appearance, following Desmazières, Di Cosmo, Lorentz (MSR 2025). Case-aggregated. citation.

179.9K

total files

77.4K

first seen 2021–2025 (43.0%)

2020

median year (half its files since)

Case variants in archive: .trigger (179.8K), .TRIGGER (48), .Trigger (27), .tRigger (1) — aggregated above.

Confirm or correct this extension

Existing claims are only secondary or weakly-attested. A confirmation (or correction) would strengthen the catalog. Vocabulary reference: docs/extension_labels.md.

Quick pick — proposed PLs. Tick one or more to auto-fill the label as pl/<id>. Each chip is a PL that upstream sources or Linguist heuristics already suggest for .trigger. Multi-tick for a polysemous extension.

Apex pl/apex via linguist · secondaryShell pl/shell via linguist · secondary

Label * If label has <...>, fill it here (e.g. for pl/<id> type rust). For multi-PL submissions, enter several pl/<id> separated by commas. Friendly name (optional) Reference URL (optional, but recommended — spec / Wikipedia / vendor) Evidence / notes *

— or, if the button is blocked, use the link just below:

(fill the form to enable this link)

What happens after I submit?

A new GitHub issue is opened in this repo with your form contents in a structured YAML block and the label ext-review. Your GitHub login becomes the annotator; the issue's created_at is the submission timestamp.
A curator script (tools/process_extension_labels.py) fetches all ext-review issues and writes their parsed contents into data/derived/extension_labels.csv with curator_status="new". Until this script runs, your submission lives only as the GitHub issue.
Your submission shows up on the curator triage page (/review/curator/) under "new". Maintainers review the issue (comment, ask for clarification, accept or reject) and edit extension_labels.csv to set curator_status to accepted.
For pl/<id> labels, build_pl_taxonomy.py promotes accepted labels into ext_claim.csv with source="manual_review:<your-login>" and strength="proposed". The next site rebuild then shows your claim on this extension's page and on the language's page.
Friendly-name + reference-URL labels (e.g. binary:image for .png) are not promoted into ext_claim.csv (they aren't PL claims) but are surfaced on this page's "Prior labels" table so anyone landing here sees them next to the auto-detected category.

In short: submitting opens an issue (provenance), and a small ingestion pipeline turns issues into rows the site renders. The loop is currently manual (the curator script must be run by a maintainer); GitHub Actions could automate it on each new issue.

Claimants (2)

Languages that list .trigger among their extensions. Strength reflects whether the upstream source treated it as their primary extension.

Language	Source	Strength
Apex	linguist	secondary
Shell	linguist	secondary

Disambiguation rules (1)

Linguist heuristics that decide, by content, which language a .trigger file actually is.

Rule	Predicts	Kind	Predicates (truncated)	Measured on SWH
`h/linguist/.trigger/0`	Apex	predicates	`[{"kind": "any", "regexes": ["(?i)^[ \\t]trigger\\s+[a-z_][a-z0-9_]\\s+on\\s+[a-z_][a-z0-9_]\\s\\(\\s(?:before\|after)\\s+(?:insert\|update\|delete\|undelete)\\b", "(?i)^[ \\t](?:public\|global)\\s+(`

SWH-mined examples (0)

No archived examples for .trigger in our local mirror yet.