-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Try out the new input submodules
#176
Comments
Also seeking feedback on this proposed change #178 to convert SSH URLs to HTTPS when an ssh-key is not supplied. |
What is the approach for checking out private submodules over SSH? That solution doesn't seem to work, unless I'm doing something totally off base here: - name: checkout hack
run: git config --global url."https://username:${{ secrets.USER_PWD }}@github.com/".insteadOf "[email protected]:"
- uses: actions/checkout@master
with:
submodules: recursive For all private submodules I receive:
|
@ericsciple (apologies, I moved my comment here since it's more of an issue discussion than PR review)
I tried that first. It only works for public submodules, the code I posted with username/password (or with a PAT) functions on a local machine. I've also tried this. No dice, I get The only thing I have been able to get functioning is to do this, which is non-ideal for a number of reasons. |
I'd appreciate a configuration option to specify a list of submodules to checkout: |
Does not work for a submodule hosted on
|
@vadi2 can you try setting |
FYI input |
This is awesome! I have been using with our org's private actions. Works great! Using via HTTPS and token. |
It seems that submodules are in detached HEAD state, is this the correct behaviour? |
I'm not sure if that's relevant to your work here, but in the end I had to revert to v1 anyway because this version was incompatible with repo-sync/pull-request#17 |
[Sorry reposting here after seeing the note on the other thread] I can give my feedback it's all good now on our end using @master, although we have an interesting case in which for some reason adding a fresh new submodule and using v2 won't work while it did work before with a submodule that was located on the root folder of the repo hmmm, anyway, all good now! Every submodule is working, please let us know when you'll have a tag ready so we can remove the dangerous master tag from CD/CI! |
If you are running it into a CD/CI pipeline I think it's the correct state, you do not want your CD/CI pipeline to have writable access to the repositories. |
Works perfect ^_^ Thanks! /cc @bas |
Thanks all for the feedback! I updated V2 to include the recent submodule/SSH changes from master. |
Did not work: - Trying with 0 fetch depth Ref: actions/checkout#176 (comment) - Use GITHUB_ACTIONS_PAT as a token: but it was used by the old eturb repo! What worked: create new personal access token - Generate: https://github.com/settings/tokens - And add the secret: https://github.com/exabl/snek5000-abl/settings/secrets/new
Collecting feedback for the new input
submodules
.Use
actions/checkout@master
. Refer here for usage.SSH support landing in master soon (tomorrow).
Will update the tag
v2
after collecting feedback. Likely next week.The text was updated successfully, but these errors were encountered: