When you ship code changes, some help-centre articles can fall behind the product. This guide shows you how to run an update check, spot articles that need edits, and refresh them so customers follow steps that still match your app.

## Prerequisites

- A project connected to your repository with published articles
- At least one code merge since your docs baseline was set

## Steps

### Step 1: Open Settings

Open your project workspace and click **Settings** in the sidebar.

### Step 2: Run an update check

In the **Check for Updates** section, leave **Target Commit (optional)** empty to compare against the latest commit, or paste a specific SHA. Click **Check for Updates** to start the analysis.

### Step 3: Review flagged articles

When the check finishes, scroll to **Recent Update Checks**. Look for **Update Needed** badges and read each suggestion's reason to see which articles may be out of date.

![Review flagged articles](https://help.supportpages.io/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6NDc3OSwicHVyIjoiYmxvYl9pZCJ9fQ==--80b5ec3776ba6c76453900769a7ecf615a3319e8/step_2.png)

### Step 4: Flag articles for refresh

For each **Update Needed** suggestion you want to fix, click **Flag**. This saves guidance on the article so regeneration knows what changed in the code.

### Step 5: Regenerate the flagged article

Click **Articles** in the sidebar, select the flagged article, and click **Regenerate**. Review the guidance, adjust it if needed, then confirm to generate a fresh draft.

### Step 6: Publish the updated article

Review the new draft in the editor. When it looks right, click **Publish** to replace the live help-centre version.

![Publish the updated article](https://help.supportpages.io/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6NDc4MCwicHVyIjoiYmxvYl9pZCJ9fQ==--bd778b7da04e1e28846bc907ee039d518d16cc7c/step_5.png)

## Tips

- You can run **Check for Updates** again any time new merges land — each run appears in **Recent Update Checks**.
- Dismiss suggestions that do not need changes so your list stays focused on real gaps.
- If screenshots in the regenerated draft look off, open the **Regenerate** dialog and turn on **Use a more powerful model**.

## Summary

Run **Check for Updates** in Settings to find stale articles after merges, **Flag** the ones worth fixing, then **Regenerate** and **Publish** from **Articles** so your help centre stays accurate.