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

Recursive Submodules #34

Closed
thorker opened this issue Sep 9, 2019 · 3 comments
Closed

Recursive Submodules #34

thorker opened this issue Sep 9, 2019 · 3 comments

Comments

@thorker
Copy link

thorker commented Sep 9, 2019

Is it possible to extend the parameters to update submodules by --recursive or make it configurable?

@TingluoHuang
Copy link
Member

try:

- uses: actions/checkout@v1
  with:
    submodules: recursive

@thorker
Copy link
Author

thorker commented Sep 9, 2019

ah, that´s it. thx

@thorker thorker closed this as completed Sep 9, 2019
@ghost
Copy link

ghost commented Sep 11, 2019

I ran into this issue too, I think other configuration options should be updated into the README, since the action.yml only mentioned that the value for this input will be false, I assumed it will only be a choice between true or false to fetch the submodules

EDIT :
Also, is there an option to add an authentication options for the submodule fetching?
Cause I'm trying to update a submodule saved within the organization, but i'm running into access rights issues. Or is this supposed to be handled by the GITHUB_TOKEN generated?

EDIT
Found solution for adding token from #14 just incase you might need it too

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

No branches or pull requests

2 participants