I'm on a Windows machine using Git 2.7.2.windows.1 with MinGW 64.
I have a script in C:/path/to/scripts/myScript.sh.
How do I execute this script from my Git Bash instance?
It was possible to add it to the .bashrc file and then just execute the entire bashrc file.
But I want to add the script to a separate file and execute it from there.
Let's say you have a script script.sh. To run it (using Git Bash), you do the following: [a] Add a "sh-bang" line on the first line (e.g. #!/bin/bash) and then [b]:
# Use ./ (or any valid dir spec):
./script.sh
Note: chmod +x does nothing to a script's executability on Git Bash. It won't hurt to run it, but it won't accomplish anything either.
./, (i.e. I did not need to run the chmod command). The ./... is explained here
./my_really_complicated_long_script_name_that_I_wish_were_autocompletable.sh), it worked. Remember to start with ./.
chmod +x [script] on git-bash (for Windows) does nothing whatsoever. Git bash is looking for the sh-bang (#!/[interpreter]), and that's what it uses to assess executablity. As such, the answer here is actually just wrong, except for the part which requires a ./ prefix, which is true for unix in general.#!/usr/bin/env sh
this is how git bash knows a file is executable. chmod a+x does nothing in gitbash. (Note: any "she-bang" will work, e.g. #!/bin/bash, etc.)
#! is called a shebang, which is a kernel convention interpreted by the shell.
If you wish to execute a script file from the git bash prompt on Windows, just precede the script file with sh
sh my_awesome_script.sh
sh my_awesome_script.sh works great for both of us either as a pre-push hook (using husky). Thanks!if you are on Linux or ubuntu write ./file_name.sh
and you are on windows just write sh before file name like that sh file_name.sh
If you're running an export command in your bash script, the above-given solution may not export anything even if it will run the script. As an alternative for that, you can run your script using
. script.sh
Now if you try to echo your var it will be shown. Check the result on git bash -
$ . setup.sh
$ echo $ALGORITHMS
[RS256]
Check more detail in this question
Once you're in the directory, just run it as ./myScript.sh
I had a similar problem, but I was getting an error message
cannot execute binary file
I discovered that the filename contained non-ASCII characters. When those were fixed, the script ran fine with ./script.sh.
I was having two .sh scripts to start and stop the digital ocean servers that I wanted to run from the Windows 10. What I did is:
Now to run the script each time I just double-click the script
If by any chance you've changed the default open for .sh files to a text editor like I had, you can just "bash .\yourscript.sh", provided you have git bash installed and in path.
#!/bin/bash at the top of the file automatically makes the .sh file executable. I agree the chmod does not do anything but the above line solves the problem. you can either give the entire path in gitbash to execute it or add it in the PATH variable export PATH=$PATH:/path/to/the/script then you an run it from anywhere
I use both Linux and Windows side by side, but favor my linux machine. so when I jump on Windows, I migrate to the command lone quickly. Gitbash uses bin/sh as their shell and it acts and feels like running bash on the linux.
Git folders are set similar to linux systems. Git is located C:\Program Files. mingw64 is also inside the Git folder and relatively close. - i'm giving you some additional steps if you haven't a;ready, but it'll make it easier for next time.
1 Create an
aliasin .bash_aliases/.bashrc
(for some it maybe .zsh)
$ sudo chmod +x /path/to/script.sh
//if you don't have one already, create an aliases file for your shell. If you're not in you ~ directory, then use the 2nd example)
$ touch .bash_aliases (~/.bash_aliases)
then open it with your text editor - usually nano or vim, there are others.
alias myscript='/path/to/script.sh'
press Ctrl` + X then y and enter to close
in ~/.bashrc
# we can call our script from anywhere
export PATH="$HOME/bin:$PATH"
# tell bashrc to read the aliases
if [ -f ~/.bash_alias ]; then
. ~/.bash_alias
fi
then Ctrl + O then Enter, the Ctrl + X to exit;
$ source ~/.bashrc
if your script isn't in your bin then symlink it
$ sudo ln -s ~/path/of/script.sh ~/bin
