From 2d2e14b341abe79a85bf89cbec89f69bfe06c0f2 Mon Sep 17 00:00:00 2001
From: Deborah Brouwer <deborah.brouwer@collabora.com>
Date: Fri, 6 Oct 2023 11:21:24 -0700
Subject: [PATCH] add some setup examples

Signed-off-by: Deborah Brouwer <deborah.brouwer@collabora.com>
---
 README.md | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8d97011..53e48bf 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,16 @@ And prepare the kernel folder locally with:
 
 ### Running the tests
 
-Once you have the image, you need to figure out the tag of the image (e.g. `docker images`).
+Once you have the image, you need to figure out the tag of the image.  
+Run the command:
+```
+docker images
+```
+You should see something like this:  
+>| REPOSITORY                                                         | TAG    | IMAGE ID       | CREATED             | SIZE     |
+>|-------------------------------------------------------------------|-------|----------------|---------------------|----------|
+>| 2023-10-06_media_build                                             | latest | c193640ac192   | About an hour ago   | 12.9GB   |
+
 
 #### Preparation
 
@@ -44,12 +53,22 @@ EOF
 
 Change the entries of the `env.sh` file accordingly to match the repository you want to test.
 
+For example:
+>myrepo=https://gitlab.collabora.com/chipsnmedia/kernel.git  
+>name="Sebastian Fricke"  
+>email="sebastian.fricke@collabora.com"  
+
+* Notice that the custom data entered in  `env.sh` does not include the name of the branch that you want to test.  
+* Instead, the name of the branch to test is supplied as an argument to `./build.sh` (see below).  
+
 #### Starting the container
 
 Now you can use that tag to enter the container:
 ```
 ./container.sh run [TAG]
 ```
+For example
+>./container.sh run 2023-10-06_media_build
 
 #### Running the tests
 
-- 
GitLab