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
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,23 +36,22 @@ GitHub action needs the following credentials for running.
36
36
37
37
Zulip API key is used for fetching the messages of public streams from the Zulip organization. We recommend creating a bot and using it's API key instead of using your own API key. See https://zulip.com/help/add-a-bot-or-integration for more details.
38
38
39
-
#### GitHub Personal Access Token
39
+
#### GitHub Token
40
40
41
-
The token is used by the GitHub action for pushing to the repo and running GitHub page builds. You can generate the token by going to https://github.com/settings/tokens. Make sure to enable `repo` and `workflow` while generating the token.
41
+
The token is used by the GitHub Actions for pushing to the repo and running GitHub page builds.
42
+
It is generated automatically by GitHub Actions itself as `secrets.GITHUB_TOKEN` and can be used right away.
42
43
43
44
### Step 3 - Store credentials as secrets in the repository
44
45
45
46
Now that we have generated the credentials, we need to store them in the repository as secrets so that action can access them during run time. For that goto `https://github.com/<username>/<repo-name>/settings/secrets`. `<username>` is your GitHub username and `<repo-name>` is the name of the repo you just created.
46
47
47
-
Now create the following 4 secrets. Use the credentials generated in the above step as the value of each secret.
48
+
Now create the following 3 secrets. Use the credentials generated in the above step as the value of each secret.
|zulip_organization_url | URL of your Zulip organization. |
52
53
|zulip_bot_email | The email of the Zulip bot you created |
53
54
|zulip_bot_key | API key of the Zulip bot you created |
54
-
|gh_personal_access_token | The GitHub personal access token you created |
55
-
56
55
57
56
### Step 4 - Configure the streams you want to index
58
57
`zulip-archive` by default don't know which all public streams to be indexed. You can tell `zulip-archive` which all streams to be indexed by creating a file called `streams.yaml` in the newly created repository. You can make a copy of a default file to start with: `cp default_streams.yaml streams.yaml`
0 commit comments