From 394e59099c89eb82cf4a37c78ab5f329b76ce0cc Mon Sep 17 00:00:00 2001
From: Mads Jensen <mje@inducks.org>
Date: Tue, 22 Dec 2015 15:28:18 +0100
Subject: [PATCH] Fixed #25936 -- Added showmigrations to migrations topic
 guide.

---
 docs/topics/migrations.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 5312b956ba..db52665067 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -24,6 +24,8 @@ and Django's handling of database schema:
 
 * :djadmin:`sqlmigrate`, which displays the SQL statements for a migration.
 
+* :djadmin:`showmigrations`, which lists a project's migrations.
+
 You should think of migrations as a version control system for your database
 schema. ``makemigrations`` is responsible for packaging up your model changes
 into individual migration files - analogous to commits - and ``migrate`` is