docs: doc repro --glob and update targets arg info.

content/docs/command-reference/repro.md

@@ -10,20 +10,22 @@ analyzing dependencies and <abbr>outputs</abbr> of the target stages.
 ```usage
 usage: dvc repro [-h] [-q | -v] [-f] [-s] [-m] [--dry] [-i]
                  [-p] [-P] [-R] [--no-run-cache] [--force-downstream]
-                 [--no-commit] [--downstream] [--pull]
-                 [targets [targets ...]]
+                 [--no-commit] [--downstream] [--pull] [--glob]
+                 [targets [<target> ...]]
 
 positional arguments:
-  targets        Stage or path to dvc.yaml or .dvc file to reproduce. Using -R,
-                 directories to search for stages can also be given.
+  targets       Limit command scope to these .dvc or dvc.yaml files,
+                or stage names.
 ```
 
+> See [`targets`](#options) for more details.
+
 ## Description
 
 `dvc repro` provides a way to regenerate data pipeline results, by restoring the
 dependency graph (a [DAG](https://en.wikipedia.org/wiki/Directed_acyclic_graph))
 implicitly defined by the stages listed in `dvc.yaml`. The commands defined in
-these stages can then be executed in the correct order, reproducing pipeline
+these stages are then executed in the correct order, reproducing pipeline
 results.
 
 > Pipeline stages are defined in a `dvc.yaml` file (either manually or by using
@@ -51,8 +53,8 @@ are run one after the other in the order they are defined. The failure of any
 command will halt the remaining stage execution, and raises an error.
 
 There are a few ways to restrict what will be regenerated by this command: by
-specifying stages as `targets`, or by using `--single-item`, among other
-options.
+specifying specific reproduction [`targets`](#options), or by using certain
+command [options](#options), such as `--single-item` or `--all-pipelines`.
 
 > Note that stages without dependencies are considered _always changed_, so
 > `dvc repro` always executes them.
@@ -97,17 +99,40 @@ up-to-date and only execute the final stage.
 
 ## Options
 
-- `-f`, `--force` - reproduce a pipeline, regenerating its results, even if no
-  changes were found. This executes all of the stages by default, but it can be
-  limited with the `targets` argument, or the `-s`, `-p` options.
+- `targets` (optional argument) - specifies one or more `dvc.yaml` files or
+  specific stage name(s). `./dvc.yaml` by default. E.g.
+  `dvc repro pipes/linear/dvc.yaml`
+
+  Stage names must be defined in `./dvc.yaml`. E.g. `dvc repro train-vision`.
+  Stages in other `dvc.yaml` files can be given using by using a colon `:`
+  following the path to that file. E.g. `models/dvc.yaml:prepare`
+
+  Different things can be provided as targets depending on the flags used (more
+  details in each option), namely:
+
+  - With `-R` you can provide directory paths to search for `dvc.yaml` files in,
+    recursively.
+  - With `--glob`, you can use special patterns (using wildcards) to match
+    groups of stage names.
+
+- `-R`, `--recursive` - looks for `dvc.yaml` files to reproduce in any
+  directories given as `targets`, and in their subdirectories. If there are no
+  directories among the targets, this option has no effect.
+
+- `--glob` - causes the `targets` to be interpreted as wildcard
+  [patterns](https://docs.python.org/3/library/glob.html) to match for stage
+  names. For example: `train-*` (certain stage names) or
+  `models/dvc.yaml:train-*` (stages in specific `dvc.yaml` file). Note that it
+  does not match patterns with the path, only to the stages present in the
+  specified file.
 
 - `-s`, `--single-item` - reproduce only a single stage by turning off the
   recursive search for changed dependencies. Multiple stages are executed
   (non-recursively) if multiple stage names are given as `targets`.
 
-- `-R`, `--recursive` - determines the stages to reproduce by searching each
-  target directory and its subdirectories for stages (in `dvc.yaml`) to inspect.
-  If there are no directories among the targets, this option is ignored.
+- `-f`, `--force` - reproduce a pipeline, regenerating its results, even if no
+  changes were found. This executes all of the stages by default, but it can be
+  limited with the `targets` argument, or the `-s`, `-p` options.
 
 - `--no-commit` - do not store the outputs of this execution in the cache
   (`dvc.yaml` and `dvc.lock` are still created or updated); useful to avoid
@@ -128,7 +153,8 @@ up-to-date and only execute the final stage.
   to. Use `dvc dag <target>` to show the parent pipeline of a target.
 
 - `-P`, `--all-pipelines` - reproduce all pipelines for all `dvc.yaml` files
-  present in the DVC project.
+  present in the DVC project. Specifying `targets` has no effects with this
+  option, as all possible targets are already included.
 
 - `--no-run-cache` - execute stage commands even if they have already been run
   with the same dependencies/outputs/etc. before.