anchor.diff:                                     |
                                      |
                                      |
  -                            build new package
  +                            build a new package
                                      |
                                      v
  -                            +----------------+
  -                           /  what change?  /
  -                          +--+-----+-----+-+
  +                          +---------------------+
  +                         /  what is changing?  /
  +                        +----+-----+-----+----+
                                |     |     |
                         +------+     |     +--------+
                         |            |              |
  
positive.code: 
  `update-patches` also supports filtering out patches based on matching a
  regex provided by a magic #patches_ignore comment in the spec file. This is
  useful, for example, in case the patches branch contains changes that are
  related to the CI/code review infra, that are useful to keep around but don't
  need to end up in the RPM.
  
  
negative.code: 
  Introduce new patches to the package.
  
  This action works with the `patches` branch
  (see <<patches-branch,AUTOMAGIC -> patches branch>>).
  
  By default, `rdopkg` resets the local patches branch to the remote patches branch.
  You can skip this with `-l`/`--local-patches` to directly use the local
  patches branch as is.
  
  Don't forget to `git fetch` before running the action.
  
  After running `rdopkg patch`, the new commit will contain the changes if there are
  any.
  
  You can use `-C`/`--changelog` option to select how `rdopkg` detects new/old
  