README: update_conda_lock: Include a pip issue information

Signed-off-by: Adam Jeliński <[email protected]>

README.md

@@ -44,6 +44,18 @@ The inputs to this action are:
 * `user_name` (default: `CONDA_LOCK_UPDATING_BOT`):
   * Name of the user creating commit.
 
+### Avoiding conflicts with inter-dependent git-based pip packages
+
+In certain circumstances pip, internally run when Conda creates the environment, might fail due to an alleged conflict in Conda Lock git-based packages.
+Until [the pip issue](https://github.com/pypa/pip/issues/10002) is fixed, it can be avoided by making pip install packages without their dependencies.
+With Conda Lock it's absolutely safe to do so since all pip packages, including the dependencies of packages specified directly, are always included in the Conda Lock.
+What's more, the package versions are all locked in Conda Lock so these dependencies can't change.
+
+Therefore currently the safest way to create Conda environment using the Conda Lock is:
+```
+env PIP_NO_DEPS="true" conda env create -f $CONDA_LOCK_FILE`
+```
+
 # Examples
 
 These are examples of using "includable" workflows. Put these in