You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `clone_git_repo_via` setting specifies via which mechanism the Git repository
493
+
should be cloned. This can be either:
494
+
*`https` (default): clone repository via HTTPS with `git clone https://github.com/<owner>/<repo>`
495
+
*`ssh`: clone repository via SSH with `git clone git@github.com:<owner>/<repo>.git`
496
+
In case of using 'ssh', one may need additional steps to ensure that the bot uses the right SSH key and does not ask for a passphrase (if the key used is protected with one). Here are a few things to consider:
497
+
- if the ssh key to be used does not have a standard name (e.g., `id_rsa`), add the following entry to `~/.ssh/config` in the bot's account
498
+
```
499
+
Host github.com
500
+
User git
501
+
IdentityFile ~/.ssh/NAME_OF_PRIVATE_KEY_FILE
502
+
```
503
+
- if the key is protected by a passphrase (**highly recommended**), run an SSH agent and add the key to it
504
+
```
505
+
eval $(ssh-agent -s)
506
+
ssh-add ~/.ssh/NAME_OF_PRIVATE_KEY_FILE
507
+
```
508
+
509
+
Note that the `bot: status` command doesn't work with SSH keys; you'll still need a Github token for that to work.
510
+
488
511
#### `[bot_control]` section
489
512
490
513
The `[bot_control]` section contains settings for configuring the feature to
0 commit comments