agent hive
Join the Waitlist

ENGINEERING

Slack approval gate before merging an upgrade with a changed HF license

When a dependency PR touches a HuggingFace model whose license changed, it holds the merge and posts an interactive Slack approval to legal/eng leads.

CategoryEngineering
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPR review approvedGitHubGitHub
  • ActionFetch current HF model licensesHugging FaceHugging Face
  • LogicBranch: license changed vs baseline?
  • ActionPost interactive Slack approval to licensing channelSlack
  • LogicBranch on approve vs reject decision
  • OutputMerge or close PR with commentGitHubGitHub

What it does

This workflow inserts a human checkpoint between detecting a HuggingFace license change and merging the PR that introduces it. When an upgrade PR is ready to merge, it re-checks each model's license; if anything changed, it posts a Slack message with Approve and Reject buttons to your licensing channel. Approve auto-merges the PR; Reject closes it and comments why. If no license changed, the PR merges with no interruption.

When to use it

Use it when license changes require sign-off rather than just a notification — common when a model flips to a commercial-use-restricted or attribution-heavy license and someone with authority must accept the terms.

How it works

  1. 1A PR review is approved on GitHub, signaling it's merge-ready.
  2. 2The workflow fetches the current license for each HuggingFace model the PR pins.
  3. 3A branch checks whether any license differs from the cleared baseline.
  4. 4If unchanged, it merges the PR directly.
  5. 5If changed, it posts an interactive Slack approval with old/new license details.
  6. 6On approval it merges; on rejection it closes the PR with an explanatory comment.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, 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.

Browse all Engineering →

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.

Join the WaitlistBrowse all workflows →