-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a Github Action to ensure variables in shell scripts are set #3343
Comments
Maybe there's a unit test framework for these shell scripts? |
|
note that my suggestion was not to create a check just for unset variables. instead, my suggestion was to create a check which ensures that i do like the ShellCheck action, though, it looks nice! |
@owaiskazi19 any proposed solutions you have that you can document so that someone can pick it up? |
Hey @minalsha! The GHA which can be used to achieve this is in the description. |
Hi @owaiskazi19! I am a first time contributor to this project. I'm familiar with GitHub actions, but I am not sure if my PR is correct. Would be possible to guide me a bit on this? I'd love to contribute to the OpenSearch project. Many thanks! |
Sure thing @laysauchoa. Welcome to OpenSearch! |
HI @laysauchoa , just following up on this issue. Do you need any help contributing to this issue? |
Can I take care of this issue? looks like something interesting |
@bl1nkker Sure. I have assigned you the issue and there's a closed PR attached for you to refer. Let us know if you need any additional information. Thanks |
Is your feature request related to a problem? Please describe.
Coming from #3106 and #3278 (comment). Create a Github Action to run on pull request to ensure whether shell scripts variables are set.
Describe the solution you'd like
Can use https://github.com/marketplace/actions/shellcheck for the same.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: