Added walkthrough for local development

Signed-off-by: Liam Barry Allan <[email protected]>

Author: worksofliam

content/code-ibmi-local/actions-create.md

@@ -0,0 +1,69 @@
+#
+
+## Creating an `actions.json` file
+
+The `actions.json` file defines what commands should be used to build your application. It belongs in the `.vscode` folder.
+
+The company_system repository comes with an existing one that uses `gmake` (GNU Make) to build the application, but you could also set up an action to:
+
+* run the `CRTBNDxxx` directory
+* run `gmake`
+* run `makei` (ibmi-bob)
+
+**You do not need a build tool** like ibmi-bob or GNU Make to compile programs.
+
+You also have access to some variables in the command:
+
+* `&CURLIB` and `&BUILDLIB` is the current library as setup in VS Code
+* `&RELATIVEPATH` is the path to the source being compiled
+* `&BASENAME` for the name and extension of the file
+* `&NAME` for just the name, useful for object parameter
+* `&USERNAME` for the currently signed in username
+
+For the errors (EVFEVENT) to be returned for the compile on the active source, `*EVENTF` must be in the command string. Notice below that `deployFirst` is set to `true` on all Actions. This is to make sure source code gets uploaded to the Deploy directory before the Action is run.
+
+#### Running an ILE command
+
+```json
+  {
+    "name": "Compile with CRTBNDRPG 🔨",
+    "command": "CRTBNDRPG PGM(&CURLIB/&NAME) SRCSTMF('&RELATIVEPATH') OPTION(*EVENTF) DBGVIEW(*SOURCE) TGTRLS(*CURRENT)",
+    "environment": "ile",
+    "deployFirst": true,
+    "extensions": [
+      "RPGLE"
+    ]
+  }
+```
+
+#### Running a pase command (make)
+
+**Note:** this would build the entire project.
+
+```json
+  {
+    "name": "Build and deploy with make 🔨",
+    "command": "/QOpenSys/pkgs/bin/gmake BIN_LIB=&CURLIB OPT=*EVENTF",
+    "environment": "pase",
+    "deployFirst": true,
+    "extensions": [
+      "GLOBAL"
+    ]
+  }
+```
+
+#### Running a pase command (ibmi-bob)
+
+**Note:** this would build the entire project. Look into use `makei compile` to build a single source.
+
+```json
+  {
+    "name": "Deploy & build with bob 🔨",
+    "command": "OPT=*EVENTF BUILDLIB=&CURLIB /QOpenSys/pkgs/bin/makei build",
+    "extensions": [
+      "GLOBAL"
+    ],
+    "environment": "pase",
+    "deployFirst": true
+  }
+```

content/code-ibmi-local/actions-results-1.png

@@ -0,0 +1,27 @@
+#
+
+## Running an Action / compiling code
+
+You can use the Control / Command + E shortcut to run an Action when you have opened some source code. This will prompt all available Actions for the current source.
+
+![](./actions-running.png)
+
+Selecting an Action with `deployFirst` as `true` will ask you which files you want to deploy:
+
+* All: deploy all sources from my local machine
+* Working changes: deploy my working changes (when git is used)
+* Staged changes: deploy my staged changes (when git is used)
+
+You should do 'All' for the first time, and then when you're confident the source is on the server you can use Working or Staged changes.
+
+![](./actions-results-1.png)
+
+You can see what happened from the Action being run here:
+
+1. it set the working home directory to the Deploy directory on the IFS
+2. It uploaded files to that directory
+3. It failed to run the command. You can click on Show Output to see the job log and spool file if there is one.
+
+![](./actions-results-2.png)
+
+If there are any source errors, you will see them appear in the editor. **This requires \*EVENTF on the Action command**.

content/code-ibmi-local/actions-results-2.png

@@ -0,0 +1,14 @@
+#
+
+## Get connected
+
+The next step is to get connect to the system where you want to compile your code. Head over to the Code for IBM i tab and either connect to a new system (red arrow) or connect to an existing one (blue arrow).
+
+![](./connect.png)
+
+The first time you connect with a folder / workspace open, it will give you two notices.
+
+* What your current library is. You can click Change to change it to the library you want to build your objects in. This is usually your own developer library.
+* If you'd like to use a default location to upload your local sources to (the 'Deploy directory'). It defaults a builds folder in the standard home directory for a user. You should select Yes. You can change this later if you wanted to.pop
+
+![](./popups.png)

content/code-ibmi-local/actions-running.md

@@ -0,0 +1,5 @@
+## Using git in Visual Studio Code
+
+Visual Studio Code has an excellent git client to go along with it. Because you are developing on the local machine, it means you can use the great git tools available.
+
+![](./git.png)