Fixed #21210 -- Documented when runserver doesn't auto-restart.

Thanks gergely at polonkai.eu for the suggestion.

2 files changed, 10 insertions, 0 deletions

diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
index 1c301c0cc2..dd40a47548 100644
--- a/docs/intro/tutorial01.txt
+++ b/docs/intro/tutorial01.txt
@@ -181,6 +181,14 @@ It worked!
     Full docs for the development server can be found in the
     :djadmin:`runserver` reference.
 
+.. admonition:: Automatic reloading of :djadmin:`runserver`
+
+    The development server automatically reloads Python code for each request
+    as needed. You don't need to restart the server for code changes to take
+    effect. However, some actions like adding files or compiling translation
+    files don't trigger a restart, so you'll have to restart the server in
+    these cases.
+
 Database setup
 --------------
 
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 9626606c01..2d9dcd9920 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -791,6 +791,8 @@ Django.)
 
 The development server automatically reloads Python code for each request, as
 needed. You don't need to restart the server for code changes to take effect.
+However, some actions like adding files or compiling translation files don't
+trigger a restart, so you'll have to restart the server in these cases.
 
 When you start the server, and each time you change Python code while the
 server is running, the server will validate all of your installed models. (See