Connections

connections.yml names the board and the repositories Mandately reads. It holds no credentials: each connection finds its token on the machine that runs the watch.

An example

mand init writes it from your answers to questions 1 and 2:

.mandately/connections.yml

board:
  kind: multica
  workspace: acme
git:
  kind: github
  repos:
    - acme/api
    - acme/web
  issue_prefix: ACME

The board

setting	what it is
`kind`	`multica`
`workspace`	your workspace's id or slug
`server`	your Multica server, only if you run your own; else Multica Cloud
`project`	one project to read, by id or name; else every project
`profile`	the `multica` command line profile whose sign-in to use; else the default one
`writes`	`false` in the watch week; `true` lets Mandately post its asks on the board

Git

setting	what it is
`kind`	`github`
`repos`	the repositories to read, as owner/name
`issue_prefix`	your board's issue key, such as `ACME`: a pull request naming ACME-12 belongs to that issue
`api`	GitHub's API address; set it for GitHub Enterprise
`agent_markers`	words that, in a commit's co-author line, mark an agent's work
`deploys`	what counts as a deploy: `deployments` (the default), `releases` or `none`
`environments`	the deployment environments that count; `production` unless you say otherwise
`writes`	`false` in the watch week; `true` lets Mandately post the merge check and its asks on pull requests
`check_context`	the merge check's name, which branch protection can require; `mandately/merge-check` unless you say otherwise

Tokens

Never put a token in this file. Mandately reads GITHUB_TOKEN or GH_TOKEN, or the GitHub command line's sign-in, and MULTICA_TOKEN, or the multica command line's sign-in. See Before you start.