GitHub Community
Running a bash script #26403
-
|
Hi there, However, now I need to run a custom script in a single repo and, I feel a separate action is too much. I’d like to be able to do run a bash script saved at ROOT/.github/script.sh but I can’t figure out how to specify the path in the run step of the workflow below.
Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 7 replies
-
|
With that setup the path to the script is relative to the root of your repository, so if your script is |
Beta Was this translation helpful? Give feedback.
-
|
Example: |
Beta Was this translation helpful? Give feedback.
-
|
Specifying the full path isn't necessary, it could even break things if you use a job container, because the path where the workspace gets mounted into the container isn't the same as on the runner VM. 😅 Best stick to the relative path, e.g.: - run: bash path/script.shSome special care might be required if you change the default working directory. 😉 |
Beta Was this translation helpful? Give feedback.
-
|
To be more explicit, you can write If you want to know the full path where the working copy resides in the runner, then you can do The absolute path should be
|
Beta Was this translation helpful? Give feedback.
-
|
I would suggest to update file access modes on git level. So you won't be required to change on every action run. git update-index --chmod=-x ./.github/script.sh |
Beta Was this translation helpful? Give feedback.
-
|
airtower-luna:
Thanks for the reply. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
what say i want to pass in a value (say from a gh secret) to the shell_script how would I do that? |
Beta Was this translation helpful? Give feedback.
-
|
Usually with an environment variable. The exact syntax will vary depending on your command, of course. Mind that anything included on the command line may be visible to other processes, so it's safer to make your script read the environment variable directly. - run: ./your_script.bash
env:
YOUR_SECRET: ${{ secrets.YOUR_SECRET }}And then look at the |
Beta Was this translation helpful? Give feedback.
-
|
yes thank you very much, i understand. |
Beta Was this translation helpful? Give feedback.
-
|
I use like this: - name: Build and Deploy Script
working-directory: ${{ github.workspace }}/PROJECT_FOLDER
run: bash ./publish-script.sh |
Beta Was this translation helpful? Give feedback.
-
|
Worked for me. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I really wish Github's documentation wasn't so terrible - why is it hard to find such fundimental information like this! |
Beta Was this translation helpful? Give feedback.
With that setup the path to the script is relative to the root of your repository, so if your script is
.github/script.shthat’s all that’s needed in the run step. Remember that the file must be marked as executable, or you need to explicitly call bash with the script as parameter.