ci: Explicitly use bash shell #4914
Conversation
It is possible for GitHub Workflows to fallback to "sh" instead of bash and since we are using bash specific features like "[[ ]]" let's explicitly declare that we want a bash shell. Signed-off-by: Thanh Ha <[email protected]>
|
@zxiiro is attempting to deploy a commit to the Meta Open Source Team on Vercel. A member of the Team first needs to authorize it. |
|
Hi @zxiiro! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
facebook-github-bot
added
the
CLA Signed
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
It is possible for GitHub Workflows to fallback to "sh" instead of bash and since we are using bash specific features like "[[ ]]" let's explicitly declare that we want a bash shell.