From 0a09941c8ef3762ac52b7f4978f8d45da228b5c4 Mon Sep 17 00:00:00 2001 From: Caroline McNamara Date: Thu, 1 Feb 2024 15:16:24 +0000 Subject: [PATCH 1/2] fix typo --- .../docs/cli-command-reference/installing-cli-tool.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/markdown-pages/docs/cli-command-reference/installing-cli-tool.md b/src/markdown-pages/docs/cli-command-reference/installing-cli-tool.md index 05a1e9de..eea73596 100644 --- a/src/markdown-pages/docs/cli-command-reference/installing-cli-tool.md +++ b/src/markdown-pages/docs/cli-command-reference/installing-cli-tool.md @@ -33,7 +33,7 @@ On Mac or Unix: 2. Download the appropriate binary of the Galasa CLI for your machine architecture from the [Galasa cli repository](https://github.com/galasa-dev/cli/releases) in GitHub and re-name it to `galasactl`. 3. Add Galasa CLI to your PATH to enable you to run CLI commands from anywhere on your file system without having to specify the absolute path. To set the path permanently, you need add the Galasa CLI path to your shell's initialization file. For example, if you downloaded the galasactl executable to a folder called `~/tools` in your home directory, you need to add `~/tools` to the list of directories that your shell searches through when you enter a command. You can do this by adding the line ```export PATH=$PATH:$HOME/tools``` to your shell’s initialization file (for example `~/.bashrc` or `~/.zshrc`). 4. Set execute permission on the binary by running the `chmod +x galasactl` command in the directory containing `galasactl`. -5. If you are using a Mac, you can set permission to open the Galasa CLI tool by running the `xattr -dr com.apple.quaranteen galasactl` command in the directory containing `galasactl`. +5. If you are using a Mac, you can set permission to open the Galasa CLI tool by running the `xattr -dr com.apple.quarantine galasactl` command in the directory containing `galasactl`. You can now run the Galasa CLI too from any directory in your file system without having to specify the absolute path. From 4ca3e8be53f15d668bbbe6340478fdbf8b146971 Mon Sep 17 00:00:00 2001 From: Caroline McNamara Date: Thu, 8 Feb 2024 09:00:48 +0000 Subject: [PATCH 2/2] update next from main --- .../docs/cli-command-reference/runs-local-debug.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md b/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md index f0e928a9..fe87b203 100644 --- a/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md +++ b/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md @@ -125,4 +125,4 @@ galasactl runs submit local --debug Read the [Viewing test results locally](viewing-test-results-cli) documentation to learn how to view the output of your test runs in your local environment. -Take a look at the [Exploring Galasa SimBank using the CLI](simbank-cli) documentation. Galasa SimBank is a component that is distributed with Galasa. SimBank simulates a mainframe application and is designed to help you to learn Galasa's basic principles of operation before you start connecting Galasa to your own mainframe application-under-test. \ No newline at end of file +Take a look at the [Exploring Galasa SimBank using the CLI](simbank-cli) documentation. Galasa SimBank is a component that is distributed with Galasa. SimBank simulates a mainframe application and is designed to help you to learn the basic principles of Galasa's operation before you start connecting Galasa to your own mainframe application-under-test. \ No newline at end of file