anchor.diff:  
   To add the environment to your build output execute `env` at the start of your build script.
   
  -```
  +```bash
   #!/bin/bash
   
   env
  
positive.code: run_my_tests
  
  # Capture the exit status of the last command in a variable
  ORIGINAL_STATUS=$?
  
  # Additional commands
  
  # Finish with the original status
  exit $ORIGINAL_STATUS
  ```
  
  ## Managing Log Output
  
negative.code: 
  ## Capturing Exit Status
  
  Scripts often contain commands that shouldn't affect the overall exit status. In this case, after choosing your main commands, you'll need to capture their exit status. Once the script finishes executing all of its commands, you will return your stored exit code. This gives you complete control over the exit code returned upon completion of the job.
  
  If you want to execute commands after your main command, but still report success/fail correctly, you’ll need to capture the exit status of your main command and then exit with it at the end.
  
  For example, the following script contains three commands:
  
  ```bash
  #!/bin/bash
  
  run_my_tests
  clean_up
  notify_team
  ``` 
  
  Running this script will exit with the status returned by the final command `notify_team`. However, both `clean_up` and `notify_team` are non-essential, and what we really care about is the outcome of the `run_my_tests` commmand. Using a variable to store the exit status (`$?`) of the test script, we can run our other commands before returning it at the end:
  
  ```bash
  #!/bin/bash
  