Rerun Arnica Status Check

Post [a] rerun on a pull request to trigger a fresh Arnica status check without retriggering other CI pipelines.

Summary

To rescan a pull request with Arnica, post [a] rerun as a standalone comment on the pull request. Arnica starts a fresh status check run for that pull request.

This works across all supported source control platforms:

• GitHub

• GitLab

• Bitbucket

• Azure DevOps

Why use [a] rerun

Pushing an empty commit also resynchronizes the pull request and retriggers other CI pipelines and workflows, which wastes time and compute.

[a] rerun refreshes only the Arnica status check. Other checks and pipelines are not restarted by this comment.

How to rerun the status check

1. Open the pull request in your source control platform.

2. Add a new comment that contains only:

[a] rerun

1. Submit the comment.

2. Wait for Arnica to queue and complete a new status check run on the pull request.

The comment must be a standalone pull request comment with the exact text [a] rerun. Do not embed the command in a longer comment or reply thread.

When to use it

Use [a] rerun when:

• The Arnica status check failed and you want Arnica to scan the pull request again.

• Policy, configuration, or finding changes should be reflected on the pull request without pushing new commits.

• You need a fresh Arnica run for any other reason.

[a] rerun does not change findings or policies on its own. It re-executes the Arnica status check for the current pull request state. If findings still match a failing policy rule, the status check can fail again after the rerun.

Related

• Code Risk Policy Settings — how pull request triggers comment on PRs and fail status checks.

• Dismissal Settings and Snooze — other Arnica pull request comment commands for dismissal workflows.

• Jobs & Tasks — restart background scan tasks from the Arnica admin UI.