ENGINEERING

Open a remediation ticket when a PR is blocked for license drift

When a PR fails the license gate, this workflow creates a tracked Linear remediation issue with the offending packages and suggested replacements, links it back to the PR.

CategoryEngineering
EngineSim + Paperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub license-gate check fails on a PRGitHubGitHub
  • ActionExtract offending packages and licenses from checkGitHubGitHub
  • ActionGenerate suggested compliant replacementsOpenAI
  • LogicDedupe against existing open remediation issue
  • ActionCreate linked Linear remediation issueLinearLinear
  • OutputEmail the PR author the summary and issue linkGmailGmail

What it does

This workflow turns a blocked PR into actionable follow-up. When a license gate rejects a pull request, it captures the non-compliant packages and their licenses, drafts suggested compliant alternatives, and opens a Linear issue assigned to the PR author. The issue links to the PR, and the author is notified by email so the remediation does not get lost after the merge is blocked.

When to use it

Use this when blocked PRs tend to stall because there is no owner or tracking. It converts each license rejection into a triaged, assigned work item with context, closing the loop between detection and fix.

How it works

  1. 1A GitHub webhook fires when a license-gate check reports a failure on a PR.
  2. 2The workflow reads the failing check details to extract offending packages and licenses.
  3. 3A step generates suggested compliant replacement packages for each violation.
  4. 4A logic step deduplicates against any open remediation issue for the same PR.
  5. 5It creates a Linear issue with the packages, licenses, and suggestions, linked to the PR.
  6. 6It emails the PR author a summary and the issue link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

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