System settings

The System tab of /settings holds two admin-only toggles that control what Gitera posts on your pull requests. Both apply to the whole organization — the setting takes effect once any admin enables it.

Pull Request CommentsCopy Anchor Link

When enabled, every PR opened or synchronize event triggers a scan of the changed files. If the PR touches a reusable workflow (a workflow_call workflow), Gitera finds every workflow in the organization that calls it and posts — or updates — a Reusable Workflow Alert comment on the PR.

The comment names the changed workflows (and whether inputs/secrets changed), lists the repositories that currently call them, and ends with a review checklist:

⚠️ Reusable Workflow Alert

This PR contains changes to reusable workflows that are currently in use
by other repositories.

Changed Workflows:
- `.github/workflows/build-reusable.yml` (changed: inputs, secrets)

Current Usage:
- my-org/payments-service (.github/workflows/deploy.yml)
- my-org/mobile-app (.github/workflows/release.yml)

Please make sure to:
- Review the changes carefully
- Test the workflow with different scenarios
- Consider the impact on the repositories above

The bot recognizes its own comment and updates it on subsequent pushes instead of stacking duplicates.

AI Failure Summary CommentsCopy Anchor Link

When enabled on a paid plan, a failed workflow run that is linked to a pull request gets an AI-generated summary posted directly on the PR — so the author sees the root cause without opening the dashboard.

The comment is a GitHub alert box followed by the evidence:

> [!CAUTION]
> **CI failed** · `ci.yml` > `test` > `Run unit tests` · seen 3×
> The coverage threshold dropped because `jest.config.ts` now excludes
> the generated client directory.
>
> **Fix:** raise the threshold include pattern back over src/generated/*.

Similar resolutions: "Coverage gate failed after jest config change" — validated

Relevant log lines  (collapsible)
   FAIL src/api/client.test.ts
   coverage for lines (82.1%) does not meet global threshold (90%)

Full log: Open in dashboard → · GitHub job
Want a deeper investigation? Comment `/rca` on this PR ...

Details to know:

• One comment per PR — a hidden marker lets Gitera update the same comment on later failures instead of stacking new ones.
• Flaky detection — once the same failure has been seen 5+ times, the alert turns yellow (Likely flaky) instead of red.
• Secrets are redacted from the root cause and log excerpt before posting.
• Similar resolutions — fixes your team documented in the failures knowledge base are attached when they match.
• Daily AI quota — posting pauses when the org's daily AI limit is reached; the failure itself is still recorded.
• The /rca hint lets anyone trigger a full Deep RCA by commenting /rca on the PR.