GitHub

Connection

Connecting sends you to GitHub to approve Klef’s access.

Permissions

Minimum permissions the connection requires.

Capability	Required	Granted by (any one)
Read members	Yes	`Members (read)`
Manage members and teams	Yes	`Members (read and write)`

github.member

Fields

Field	Type	Required	Description
`login` (Username)	string, up to 39	Yes	The person’s GitHub username. The account belongs to them.
`member`	bool		Whether the person belongs to the organization.
`role`	enum		Role in the organization. Values: `member` (Member), `admin` (Owner).
`teams`	grant		Teams the member belongs to. One row grants one team.
`teams[]`	string		Team slug.

Default Account Matching Rules

When Klef adopts an account that already exists in GitHub, it works out whose it is by trying these in order. A connection can override them.

Account field	Worker field
`login`	`worker.login`

Examples

Engineering access

The engineering group, a seat on the GitHub engineering team and the incident channels, with GitHub removed when they leave.

stage active {
  target github.member {
    login  = lookup(table.github_usernames, worker.business_email)
    member = true
    role   = "member"
    teams  = ["engineering"]
  }
}

Leaver offboarding

Ask the manager to plan the handover, then close Microsoft, Slack and GitHub access on the last day and tell security.

stage terminated {
  target github.member {
    login  = lookup(table.github_usernames, worker.business_email)
    member = false
    teams  = []
  }
}

Basics

Connectors

Administration

GitHub

GitHub

Connection

Permissions

github.member

Fields

Default Account Matching Rules

Examples

Engineering access

Leaver offboarding

​GitHub

​Connection

​Permissions

​github.member

​Fields

​Default Account Matching Rules

​Examples

​Engineering access

​Leaver offboarding

GitHub

Connection

Permissions

github.member

Fields

Default Account Matching Rules

Examples

Engineering access

Leaver offboarding