Skip to content
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

Merged
merged 7 commits into from
Jan 7, 2022
Merged

no default shell in composite actions #44

merged 7 commits into from
Jan 7, 2022

Conversation

scottyhq
Copy link
Contributor

@scottyhq scottyhq commented Jan 6, 2022

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)

@jomey
Copy link
Contributor

jomey commented Jan 6, 2022

Curious why the check was skipped?

@jomey
Copy link
Contributor

jomey commented Jan 6, 2022

Should we also add the cookiecutter directory to the test.yaml paths?

@scottyhq
Copy link
Contributor Author

scottyhq commented Jan 6, 2022

Should we also add the cookiecutter directory to the test.yaml paths?

Good call. Might run into issues with the odd folder name {{ cookiecutter.repo_directory }}

@scottyhq
Copy link
Contributor Author

scottyhq commented Jan 6, 2022

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.

@jomey jomey mentioned this pull request Jan 7, 2022
@jomey jomey self-requested a review January 7, 2022 14:40
@jomey
Copy link
Contributor

jomey commented Jan 7, 2022

@JessicaS11 - Are you OK with merging this and follow up with another PR to fine-tune the trigger actions?

@jomey jomey merged commit b409051 into main Jan 7, 2022
@jomey jomey deleted the actions2 branch January 7, 2022 17:08
jomey pushed a commit that referenced this pull request Apr 6, 2022
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
jomey pushed a commit that referenced this pull request Apr 6, 2022
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
jomey pushed a commit that referenced this pull request Apr 6, 2022
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
jomey pushed a commit that referenced this pull request Apr 6, 2022
Since scientific Python packages following NEP29 should have deprecated Python 3.7 as of 26 Dec 2021.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants