Connect your services
Back to the user guide.
Every service has a connection section in Settings (press ,). They all look alike:
| Row | What it is |
|---|---|
| (found) | a question, if radar found a token in your environment |
| server, site or workspace | where the service is |
| token | env:NAME to read an environment variable each time, or the token itself |
| signed in as | who the service says the token belongs to, from the last check |
| check | what the last check said. ⏎ runs it now |
| refresh | how often radar asks the service for changes |
A service may add rows of its own below these, such as GitLab’s access and the groups or repositories to follow.
Move to a row and press ⏎ to change it. While you type, the right pane says what the
field accepts and whether what you typed is valid. After you change a connection, radar offers
to check it: it asks the service who you are and tells you whether it works.
Where tokens are kept. env:NAME stores the variable’s name, and radar reads its value
each time it starts. A token you type or paste is saved in the config file (radar config path
says where) and shown masked.
In setup or in Settings. Setup’s step for a service (radar setup gitlab, github,
jira, slack) shows this same connection section, so both edit the same fields. Beside it,
setup shows help for the selected row and how to get a token, with links: o opens the
token page, y copies a command.
Tokens radar finds
Each service’s connection section checks your environment variables. When it finds something that looks like a token for that service, it asks:
? Found in your environment: a Slack user token (SLACK_TOKEN). Use it?
⏎ uses it (in setup, space, because ⏎ moves on). radar then saves the variable’s name,
as env:SLACK_TOKEN. The question stays until the service is signed in.
| Service | It offers |
|---|---|
| GitLab | GITLAB_TOKEN, when the token is set to something else and its value is 20 characters or more (env:GITLAB_TOKEN is the default, so it is usually already in use) |
| Jira | a set of variables with a common prefix that has JIRA or ATLASSIAN in it: a _BASE_URL (or _URL), an _EMAIL (or _USERNAME, _USER) and a _TOKEN (or _API_TOKEN) |
| Slack | a variable whose name has SLACK and TOKEN, and whose value starts with xoxp- (a user token) |
| GitHub | nothing in Settings; setup’s look for keys notices GITHUB_TOKEN, GH_TOKEN and gh’s sign-in, and its GitHub step offers gh |