-
Notifications
You must be signed in to change notification settings - Fork 6
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
no default shell in composite actions #44
Conversation
Curious why the check was skipped? |
Should we also add the cookiecutter directory to the |
Good call. Might run into issues with the odd folder name |
I think this is good to go now, thanks for the helpful comments! I wouldn't be surprised if it requires one more followup to get CI fully working again. |
@JessicaS11 - Are you OK with merging this and follow up with another PR to fine-tune the trigger actions? |
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
Follow-on to #42
Any 'run' command in github actions needs the shell type (bash) specified
actions/runner#646 (comment)
Also need to pass secrets as inputs (https://stackoverflow.com/questions/70098241/using-secrets-in-composite-actions-github)