Скачать или смотреть How to Use GitHub Actions to Download Multiple Private Submodules with Separate SSH Keys

This guide covers a straightforward solution to downloading multiple private submodules in a GitHub Actions workflow, utilizing separate SSH keys effectively.
---
This video is based on the question https://stackoverflow.com/q/69076098/ asked by the user 'This-is-patriiick' ( https://stackoverflow.com/u/16843804/ ) and on the answer https://stackoverflow.com/a/70078472/ provided by the user 'This-is-patriiick' ( https://stackoverflow.com/u/16843804/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: GitHub Actions with multiple private submodules

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
The Challenge of Using GitHub Actions with Private Submodules

When working with GitHub Actions, you might encounter situations where you need to download private submodules from multiple repositories. These submodules could hold critical components of your project, and accessing them is crucial for your CI/CD workflow. The challenge arises when you need to authenticate each of these private submodules with separate SSH keys.

In this guide, we'll tackle the problem of downloading two private submodules using their associated SSH keys in GitHub Actions, providing you with a step-by-step guide to get it done effectively.



The Initial Attempt

You may start with a setup like this:

[[See Video to Reveal this Text or Code Snippet]]

While this configuration seems logical, you'll often find that the folders for repo_1 and repo_2 are created, but remain empty. This is a common frustration, especially when each submodule requires its own SSH key for access.

A Working Solution

Fortunately, there's a practical workaround to download multiple private submodules effectively using GitHub Actions. The key is to switch between HTTPS and SSH for your Git configurations during the workflow process. Below, we’ll break down the solution into easy-to-follow steps.

Step 1: Switch to HTTPS Git Configuration

First, you need to configure Git to work with HTTPS and unset any existing SSH settings. This setup prepares your environment for the subsequent SSH configuration.

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Checkout the Main Repository

Using actions/checkout, you can check out the primary repository without considering the submodules yet.

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Switch Back to SSH Git Configuration

After checking out the main repository, you need to revert back to an SSH setup. This ensures that the subsequent commands can operate using SSH keys.

[[See Video to Reveal this Text or Code Snippet]]

Step 4: Check Out Submodules with SSH Keys

Now, we’ll proceed to check out each submodule one at a time using their respective SSH keys.

You need to use ssh-agent to manage your SSH keys effectively during this process.

[[See Video to Reveal this Text or Code Snippet]]

Explanation of the Checkout Process

eval \ssh-agent -s``: This command starts the SSH agent, which will handle your SSH keys securely.

ssh-add -D: This removes all identities from the SSH agent after each submodule is checked out to prevent any potential conflicts.

GIT_SSH_COMMAND: Specifies to bypass the strict host key checking for the SSH session, which can ease the process during automated workflows.

Conclusion

By following these steps, you can successfully download multiple private submodules with separate SSH keys using GitHub Actions. This method allows for a more organized and secure way to handle authentication, ensuring that your workflows run smoothly and efficiently.

With this approach, you are not only solving the initial problem but also enhancing your skills in GitHub Actions. Happy coding!