mirror of
https://github.com/schpet/linear-cli.git
synced 2026-09-14 14:26:50 +08:00
Magnus Buvarp
9e0874847e
## Summary This improves `linear issue create` in three related areas: - allow `--project` to keep issue creation interactive, the same way `--parent` already does - add optional project selection in interactive issue creation - add configurable default self-assignment behavior for created issues Before this change, `linear issue create --project "Dashboard"` skipped interactive mode and failed with "Title is required when not using interactive mode". With this PR, `--project` is treated as an interactive-safe input, so users can preselect a project without also needing `--title`. Project prompting in interactive mode remains opt-in. `issue_create_ask_project` defaults to `false`, so existing interactive behavior is unchanged unless users explicitly enable the new prompt. ## Changes - allow interactive issue creation when the only flags are `--project`, `--parent`, or both - add a team-scoped project picker during interactive issue creation - gate the direct project prompt behind a new config option: `issue_create_ask_project` - keep `issue_create_ask_project = false` as the default, so project selection stays out of the main interactive flow unless enabled - when `issue_create_ask_project = false`, expose `Project` through the existing "Add more fields" flow instead - continue inheriting the parent issue's project when `--parent` is used without an explicit `--project` - allow explicit `--project` together with `--parent` and defer any invalid combination checks to the Linear API - add a new config option, `issue_create_assign_self`, with these modes: - `auto` (default): respect Linear's `autoAssignToSelf` setting - `always`: default-assign created issues to self - `never`: never default-assign created issues - update docs for the new interactive behavior and config options ## Notes - `issue_create_ask_project` defaults to `false`, so users who do not set it will keep the previous interactive flow - project selection only shows projects available to the selected team - the interactive project picker is not shown when a parent issue is present unless the project was explicitly provided - explicit `--assignee`, the interactive assignee flow, and `--start` still override the default assignment behavior ## Testing - `deno task codegen` - `deno task check` - `deno lint` - `deno fmt` - `deno task generate-skill-docs` - `deno test --allow-all --quiet test/config.test.ts` - `deno test --allow-all --quiet test/commands/issue/issue-create.test.ts`
148 lines
4.4 KiB
Markdown
148 lines
4.4 KiB
Markdown
# authentication
|
|
|
|
the CLI supports multiple authentication methods with the following precedence:
|
|
|
|
1. `--api-key` flag (explicit key for single command)
|
|
2. `LINEAR_API_KEY` environment variable
|
|
3. `api_key` in project `.linear.toml` config
|
|
4. `--workspace` flag → stored credentials lookup
|
|
5. project's `workspace` config → stored credentials lookup
|
|
6. default workspace from stored credentials
|
|
|
|
## stored credentials (recommended)
|
|
|
|
API keys are stored in your system's native keyring (macOS Keychain, Linux libsecret, Windows CredentialManager). workspace metadata is stored in `~/.config/linear/credentials.toml`.
|
|
|
|
### commands
|
|
|
|
```bash
|
|
linear auth login # add a workspace (prompts for API key)
|
|
linear auth login --key <key> # add with key directly (for scripts)
|
|
linear auth list # list configured workspaces
|
|
linear auth default # interactively set default workspace
|
|
linear auth default <slug> # set default workspace directly
|
|
linear auth logout <slug> # remove a workspace
|
|
linear auth logout <slug> -f # remove without confirmation
|
|
linear auth whoami # show current user and workspace
|
|
linear auth token # print the resolved API key
|
|
```
|
|
|
|
### adding workspaces
|
|
|
|
```bash
|
|
# first workspace becomes the default
|
|
$ linear auth login
|
|
Enter your Linear API key: ***
|
|
Logged in to workspace: Acme Corp (acme)
|
|
User: Jane Developer <jane@acme.com>
|
|
Set as default workspace
|
|
|
|
# add additional workspaces
|
|
$ linear auth login
|
|
Enter your Linear API key: ***
|
|
Logged in to workspace: Side Project (side-project)
|
|
User: Jane Developer <jane@example.com>
|
|
```
|
|
|
|
### listing workspaces
|
|
|
|
```bash
|
|
$ linear auth list
|
|
WORKSPACE ORG NAME USER
|
|
* acme Acme Corp Jane Developer <jane@acme.com>
|
|
side-project Side Project Jane Developer <jane@example.com>
|
|
```
|
|
|
|
the `*` indicates the default workspace.
|
|
|
|
### switching workspaces
|
|
|
|
```bash
|
|
# set a new default
|
|
linear auth default side-project
|
|
|
|
# or use --workspace flag for a single command
|
|
linear --workspace side-project issue list
|
|
linear --workspace acme issue create --title "Bug fix"
|
|
```
|
|
|
|
### credentials file format
|
|
|
|
```toml
|
|
# ~/.config/linear/credentials.toml
|
|
default = "acme"
|
|
workspaces = ["acme", "side-project"]
|
|
```
|
|
|
|
API keys are not stored in this file. they are stored in the system keyring and loaded at startup.
|
|
|
|
### platform requirements
|
|
|
|
- **macOS**: uses Keychain via `/usr/bin/security` (built-in)
|
|
- **Linux**: requires `secret-tool` from libsecret
|
|
- Debian/Ubuntu: `apt install libsecret-tools`
|
|
- Arch: `pacman -S libsecret`
|
|
- **Windows**: uses Credential Manager via `advapi32.dll` (built-in)
|
|
|
|
if the keyring is unavailable, set `LINEAR_API_KEY` as a fallback.
|
|
|
|
### migrating from plaintext credentials
|
|
|
|
older versions stored API keys directly in the TOML file. if the CLI detects this format, it will continue to work but print a warning. run `linear auth login` for each workspace to migrate keys to the system keyring.
|
|
|
|
## environment variable
|
|
|
|
for simpler setups or CI environments, you can use an environment variable:
|
|
|
|
```sh
|
|
# bash/zsh
|
|
export LINEAR_API_KEY="lin_api_..."
|
|
|
|
# fish
|
|
set -Ux LINEAR_API_KEY "lin_api_..."
|
|
```
|
|
|
|
this takes precedence over stored credentials. if you have `LINEAR_API_KEY` set and try to use `linear auth login`, you'll see a warning:
|
|
|
|
```
|
|
Warning: LINEAR_API_KEY environment variable is set.
|
|
It takes precedence over stored credentials.
|
|
Remove it from your shell config to use multi-workspace auth.
|
|
```
|
|
|
|
## project config
|
|
|
|
you can also set the API key in a project's `.linear.toml`:
|
|
|
|
```toml
|
|
api_key = "lin_api_..."
|
|
workspace = "acme"
|
|
team_id = "ENG"
|
|
issue_create_assign_self = "always"
|
|
issue_create_ask_project = true
|
|
```
|
|
|
|
this is useful for project-specific credentials but less secure than stored credentials since it may be committed to version control.
|
|
|
|
## workspace matching
|
|
|
|
when your project config has a `workspace` setting:
|
|
|
|
```toml
|
|
# .linear.toml
|
|
workspace = "acme"
|
|
team_id = "ENG"
|
|
```
|
|
|
|
the CLI will automatically use the stored credentials for that workspace, even if a different workspace is your default. this lets you work on multiple projects with different workspaces without constantly switching.
|
|
|
|
## creating an API key
|
|
|
|
1. go to [linear.app/settings/account/security](https://linear.app/settings/account/security)
|
|
2. scroll to "Personal API keys"
|
|
3. click "Create key"
|
|
4. give it a label (e.g., "CLI")
|
|
5. copy the key (starts with `lin_api_`)
|
|
|
|
note: creating an API key requires member access; it is not available for guest accounts.
|