ENGINEERING
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened with model changesGitHub
- ActionExtract added HF model IDs from diffGitHub
- ActionResolve license and gated statusHugging Face
- LogicRoute only risky or unknown licenses
- OutputCreate Linear license-review issueLinear
What it does
Turns a borderline license into a tracked review task instead of a blocking wall. When a Hugging Face model dependency lands with a copyleft, custom, gated, or missing license, this workflow creates a Linear issue so a human reviewer can make the call, with all the context already gathered.
When to use it
Use it when your policy is "escalate, don't auto-block" — teams that want legal or eng-lead sign-off on questionable licenses rather than a hard merge gate. Pairs well with a hard-block workflow that handles the clearly-forbidden cases.
How it works
- 1A GitHub pull request event triggers the run.
- 2Newly added Hugging Face model IDs are pulled from the diff.
- 3The Hugging Face API resolves each model's license and gated status from its model card.
- 4A logic step routes only licenses that are non-permissive, custom, gated, or undeclared into the escalation path; clean permissive licenses exit quietly.
- 5A Linear issue is created on the license-review team with the model name, license tag, PR author, and PR URL, labeled for triage.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
Warn the engineer in Slack when a model license is non-commercial
On a PR that adds a Hugging Face model, it checks the license and, if it is non-commercial or research-only, sends the PR author a direct Slack message explaining the restriction…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.