self-hosted not using bashrc

[alexhraber]

I can source it, but by default nothing from bashrc is loaded into the runtime at launch.

Should I update a different file instead bashrc? We have several additions to our base image to support multiple engineering workflows and dependencies, including a rather lengthy PATH.

I’ve suggested people source bashrc, but typically this is something that is expected in the linux world that when you have a shell, the environment loads with any configurations.

Is there any plan to automatically source bashrc? 

[Yanjingzhu]

Hi @everops-alex , 

Currently Github Actions invoke bash scripts in non-interactive mode, it will not load .bashrc by default.  

>> Is there any plan to automatically source bashrc? 

I would recommend you submiting this requirement in the Feedback form for GitHub Actions. 

[Jackenmen]

You can use custom shell, @everops-alex:

https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#custom-shell

For example, the template of “bash” shell is:

bash --noprofile --norc -eo pipefail {0}

So to make it source the rc files before running the script, you can use (-l flag is needed to invoke bash as login shell, see “Invocation” section in bash’s man page for more info):

bash -leo pipefail {0}

_Edited: _I used -I instead of -l in the reply

[AllanOricil]

Does not work on my self-hosted runner

this is my bash version

[FaureAlexis]

Hello @AllanOricil,
There is a typo in your shell property : It's -leo not -ieo (-l for login)

[snakajima-cogility]

Heads up this prevents early exit with exit 0.

[xavierLowmiller]

Is it possible to set this for the whole workflow?

[Yanjingzhu]

You could use defaults.run to provide default shell options for all run steps in a workflow.

name: use bashrc
defaults:
  run:
    shell: bash -ieo pipefail {0}
on: 
 push:
jobs: 
  job1:
    ......

[devzer01]

the shell is declared as enum you can only type bash cant provide arguments

[devzer01]

ah my bad i just read the error message again Invalid shell option. Shell must be a valid built-in (bash, sh, cmd, powershell, pwsh) or a format string containing '{0}'