> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rapidreview.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Correct or remove a learning

> How to correct, remove or bring back a Rapid Review learning by replying in its GitHub thread, and why a learning gets retired or replaced; read this when a learning is wrong, no longer holds, was retired, or you want it back.

## How do I remove a learning?

With write access to the repository, reply `@rapidreview-dev forget` in the GitHub thread the learning came from, as the whole reply. Rapid Review reacts with a thumbs up and replies "Removed." Later reviews no longer use the learning.

## How do I correct a learning, or say it no longer holds?

With write access to the repository, reply in the learning's thread and say what's wrong with it, or that it no longer holds. Rapid Review reads the reply and either rewrites the learning from the whole thread, announcing the new version with "Learning updated for later reviews of this repository:", or removes it with "Removed."

## What happens if I edit or delete the reply a learning came from?

Editing the reply a learning came from makes Rapid Review read the thread again. The learning stays the same, is replaced by a different one, or is retired if the thread no longer gives one. Deleting that reply retires the learning.

## Why was a learning retired?

A learning can be retired on its own. Its thread then says so, in a reply that starts "Learning retired:":

* **Its pull request was closed without merging.** Reopening the pull request brings the learning back, and its thread says so.
* **A later push fixed the learning's finding in a way that goes against the learning.**

## How do I bring back a retired learning?

Reply `@rapidreview-dev keep` in the learning's thread, as the whole reply. Rapid Review reacts with a thumbs up and replies "Kept." A learning that waited for a person before it was retired waits again.

For a learning retired because its pull request was closed without merging, reopening the pull request also brings it back.

## What happens when a later pull request goes against a learning?

When a thread on a later pull request goes against an earlier learning, Rapid Review can retire that learning, or replace it with what the new thread teaches. It says so in the later thread and links the learning's own thread. Replying there that the learning still holds can restore it; Rapid Review then replies "Restored."

## Can I delete a learning for good?

Only Rapid Review can delete a learning for good. A deleted learning isn't learned again from its threads.

To stop a learning from being used, reply `@rapidreview-dev forget` in its thread.

## Can I change learnings in the Rapid Review app?

You change a learning by replying in its GitHub thread: reply `@rapidreview-dev forget` to remove it, `@rapidreview-dev keep` to bring back a retired one, or say what's wrong with it to correct it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.