Linux – Command not executing inside shell script

There are a few things I can think of.

1. You said your script is in your $PATH, yet you call it with its full path (./gitup as opposed to just gitup). Could it be that you have edited one version of the script (the one in your $PATH, say ~/bin/gitup) and have then executed another (./gitup)?

2. Could there be multiple versions in your $PATH? You can check with

   which -a gitup
   

3. You may have inadvertently entered a strange invisible character while editing the script. Check the shebang line using od:

   head -1 ./gitup | od -c
   

   Make sure there is nothing after #!/bin/bash but the newline character (\n). It should look like this:

   0000000   #   !   /   b   i   n   /   b   a   s   h  \n
   0000014
   

There are three options I use when I have a bash script that I want to behave differently when it is sourced vs. when it is executed (or in other words have data items in a script that I want access to without executing any code at that time). The comments touched on them to an extent.

Option One

Determine when being sourced and end 'sourcing' at appropriate time

Separate script into two sections, exit from script when sourced before getting to lower second

Create an upper section of script with definitions (functions / variable assignments / etc), but no direct code execution.

Just before the executable code section starts, place logic that will exit the script if it detects it is being sourced. The following code segment will do this:

file1.sh

#!/usr/bin/env bash
export var1="/data/share"
export var2='password'    
# --- End Definitions Section ---    
# check if we are being sourced by another script or shell
[[ "${#BASH_SOURCE[@]}" -gt "1" ]] && { return 0; }
# --- Begin Code Execution Section ---
echo "Hello"
echo $var1
echo $var2 

file2.sh

#!/usr/bin/env bash 
source file1.sh
echo "$var1"
echo "$var2"

Output of running ./file2.sh

$ ./file2.sh 
/data/share
password

Option Two

This one is usually only used in complex situations, and for this particular example it's overkill. I create a function in the file that I want to source, and in that function determine what should be available to the caller. In this case it's the two exported variables. Normally I use this mode when I have associative arrays, which are otherwise nearly impossible to hand around. Also, the tmp file should be deleted by the caller; but I didn't in this case:

file1.sh

#!/usr/bin/env bash 
export var1="/data/share"
export var2='password'
exportCfg() {
  tmpF=$(mktemp)
  declare -p var1 var2 > "$tmpF"
  echo "$tmpF"
}
if [ "$1" == "export" ]; then
  exportCfg;
  exit 0;
fi

echo "Hello"
echo $var1
echo $var2

file2.sh

#!/usr/bin/env bash 
source $(./file1.sh export)


echo "$var1"
echo "$var2"

The output from executing file2.sh is the same as above

Option 3

The final common way I handle this is simply with a library file that only holds definitions, and has no code that will execute when sourced or directly run. This is simply a matter of dividing up your code. I have a group of bash 'libs' that contain frequently used functions, and on a per project basis usually setup a small sourceable library for storing configuration data (constants). If that data includes populated arrays, then I will also use a version of Option 2.