From 1f8557300df67dc30e700a9ea17beecd63fc5c2f Mon Sep 17 00:00:00 2001 From: beckerinj Date: Tue, 28 Feb 2023 01:33:55 -0500 Subject: [PATCH] fix type --- docs/builds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/builds.md b/docs/builds.md index 6b26a7011..b56a2bfbc 100644 --- a/docs/builds.md +++ b/docs/builds.md @@ -21,7 +21,7 @@ Just as with private repos, you will need to select a docker account to use with Sometimes a command needs to be run before running ```docker build```, you can configure this in the *pre build* section. -There are two fields to pass for *pre build*. the first is *path*, which changes to working directory. To run the command in the root of the repo, just pass ```.```. The second field is *command*, this is the shell command to be executed after the repo is cloned. +There are two fields to pass for *pre build*. the first is *path*, which changes the working directory. To run the command in the root of the repo, just pass ```.```. The second field is *command*, this is the shell command to be executed after the repo is cloned. For example, say your repo had a folder in it called "scripts" with a shell script "on-clone.sh". You would give *path* as "scripts" and command as "sh on-clone.sh". Or you could make *path* just "." and then command would be "sh scripts/on-clone.sh". Either way works fine.