← Back to blog

GitHub

Stop Design Drift Before It Merges: GitHub Checks From DesignGuard

DesignGuard AI6 min read

Here's a story that will sound familiar. A developer is in a hurry, needs a blue that looks like your brand blue, and types the hex code straight into the stylesheet. It works. It looks right. The pull request gets approved because nobody on the team can eyeball the difference between two blues.

Three months later your brand blue changes, and that one screen stays stubbornly the old color. Nobody did anything wrong. There was just no one in the room at the moment it mattered.

That moment is the pull request. So that's where DesignGuard now shows up.

What happens when someone opens a pull request

Once you connect a repository, DesignGuard listens to GitHub. When a PR is opened or a new commit is pushed, it runs its checks and posts the result as a normal GitHub check, the same kind of green tick or red cross you already see from your tests.

Someone opens a PR

Or pushes a new commit to it

GitHub tells DesignGuard

Within a second or two

The checks run

Design drift, code drift, Code Connect

A green, grey or red check

Right on the PR, with a short summary

Nobody has to remember to run anything. The check just shows up on the pull request.

There is nothing for the developer to install and nothing to remember to run. They just see an extra line on their pull request, with a short summary of what DesignGuard found.

Three checks, three different questions

We split this into three separate checks, because they answer three different questions and you may only want some of them.

  • Code Drift looks at the code in the PR and asks: did this add a hard-coded color, an off-scale spacing value, an odd font size, a one-off corner radius, or a plain native element where a design system component should be? It only reads the lines the PR adds, so old code never gets blamed on the new author. Test files, stories and type definitions are skipped.
  • Design Drift looks at the bigger picture: are there open findings in your workspace that are serious enough to block a release? It reads the same findings you see on the Findings page.
  • Code Connect asks a narrower question: this PR changed a component that exists in Figma. Does it have a Code Connect file, so designers and developers stay linked? If not, it says which component needs one.

Code Drift is the one most teams notice first, because it gives line-by-line feedback. The problem lines are annotated directly in the PR's Files changed tab, so the fix is usually a thirty-second job.

You decide how strict it is

Nobody likes a new check that suddenly blocks everyone's work. So every check has three modes, and you set the mode for each repository separately.

Off

The default. DesignGuard stays silent on this repo.

Report only

Posts a grey check with what it found. Never blocks the merge.

Required

Goes red when a serious issue is found. The merge is blocked.

Set per repository, per check. Most teams start on Report only for a couple of weeks.
  • Off is the default. Nothing happens until you turn it on.
  • Report only posts a grey check with the findings. It never stops a merge. This is where we suggest everyone starts.
  • Required turns the check red when it finds something at or above your blocking severity. Which severities count as blocking is a workspace setting, so you control how picky it is.

A rollout that has worked well: switch on Report only everywhere, leave it for a week or two, and see what it actually flags. If the noise is low and the findings are real, move the repositories you care most about to Required.

One thing to know about Required

Required mode makes the DesignGuard check fail. To actually stop the Merge button, you also add that check to your branch protection rules in GitHub (Settings, Branches, then require status checks). DesignGuard deliberately doesn't change your branch protection for you. That's your repository and your call.

What it won't do

  • It won't rewrite your code. It points at the problem and says what the approved value is.
  • The Design Drift check looks at the whole workspace, not just the files in the PR, because findings aren't tied to individual files. That means it can mention drift that was there before the PR. The idea is to clear it once and then stay clean.
  • Very large PRs are capped at 300 scanned files, and files over 200 KB are skipped. The summary tells you when that happened, so you're never left guessing.

Getting started

Open Settings, then Integrations, then GitHub, and connect the DesignGuard GitHub App on the repositories you want. Each connected repository has a drop-down for each check. Pick Report only, open a pull request, and look at the check that appears. That's the whole setup.

If a developer is going to see a message about a design rule, it's much kinder for them to see it while the code is still fresh in their head than three months later in an audit. That's all this is: moving the conversation to the moment it's cheapest to have.

See it on your own design system

Run a DesignGuard AI audit against a real Figma frame or repo.

Open dashboard

More posts

Keep reading.

View all posts

Product updates

Projects: Keep One Workspace Clean Across Many Products

Read post

Product updates

The Design Token That Never Became a Rule

Read post

Product updates

Reach and Frequency Are Now Badges, Not a Sentence You Have to Parse

Read post