Skip to content

Commit 114f7b3

Browse files
committed
Describe how to obtain the app_id and installation_id
1 parent c9ecbc6 commit 114f7b3

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

README.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ singularity pull docker://deltaprojects/smee-client
7777
singularity run smee-client_latest.sif --url https://smee.io/CHANNEL_ID
7878
```
7979

80-
## Step 2: Registering GitHub App
80+
## <a name="step2"></a>Step 2: Registering GitHub App
8181

8282
We first need to register a GitHub App, link it to the Smee.io channel, set a secret token to verify the webhook sender, set some permissions for the app, subscribe it to selected events and define that this app should only be installed in your account.
8383

@@ -186,6 +186,10 @@ private_key = FULL_PATH_TO_PRIVATE_KEY
186186
build_job_script = PATH_TO_BOT_REPO/scripts/eessi-bot-build.slurm
187187
```
188188

189+
You will also need to set the `app_id` and the `installation_id`. You find the id of your GitHub App via the page [GitHub Apps](https://github.com/settings/apps). On this page, select the app you have registered in [Step 2](#step2). On page of the app you will find the `app_id` listed as 'App ID'. For the `installation_id` select 'Install App' in the menu on the left-hand side. Then click on the gearwheel button of the installation (to the right of the 'Installed' label). The URL of the resulting page contains the `installation_id` -- the number after the last '/'.
190+
191+
Replace default values for `app_id` and `installation_id` in `app.cfg` with the values you have obtained as described above.
192+
189193
### Step 5.6: Run the EESSI bot
190194

191195
Change directory to `eessi-bot-software-layer` (which was created by cloning the repository in Step 5.4 - either the original one from EESSI or your fork). Then, simply run the bot by executing

0 commit comments

Comments
 (0)