ENGINEERING
HuggingFace license-change blocker to GitHub issue
Watches the license field of in-use HuggingFace models and, when a license flips to a more restrictive or non-commercial term, opens a high-priority GitHub issue and posts…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch license fields for watched modelsHugging Face
- LogicFlag only moves to restrictive/non-commercial licenses
- ActionOpen blocker GitHub issue with license deltaGitHub
- OutputPost compliance alert to SlackSlack
What it does
Focuses narrowly on the legal risk: the `license` and license-name tags on the HuggingFace cards of the models you ship. When a model moves from a permissive license (Apache-2.0, MIT) to anything more restrictive, non-commercial, or gated, it raises an urgent GitHub issue in your compliance repo and pings the engineering channel so the model isn't shipped under terms you no longer satisfy.
When to use it
Use it if your commercial product embeds open weights and a relicense (which has happened to major model families) could expose you to legal liability. This is the fast-path alarm, separate from routine card drift.
How it works
- 1A schedule triggers the daily check.
- 2It pulls the current license fields for every model on the watchlist from HuggingFace.
- 3A logic step classifies each license and flags only transitions toward more-restrictive or non-commercial terms.
- 4For each flagged model it opens a GitHub issue labeled `legal` / `blocker` with the old and new license.
- 5It posts a summary alert to Slack linking the issue so the team sees it immediately.
Set it up
What you configure once, before turning it on.
- 1Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
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.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.