Skip to content

feat: defer and target — dbt commands run with --defer --state, /defer and /target - #28

Open
hkaltai wants to merge 9 commits into
mainfrom
feat/defer-target
Open

hkaltai wants to merge 9 commits into
mainfrom
feat/defer-target

Conversation

@hkaltai

@hkaltai hkaltai commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

What this does

Package P-04 (plugin half). When the project's dbt Power User defer setting is on, the dbt commands Claude runs get --defer --state <dir> (and --favor-state when set) inserted right after the subcommand.

  • hooks/features/defer.tsx: reads the setting once per session, on first need, through the dbt_defer_state tool (altimate-code PR feat: dbt_defer_state tool — Power User defer setting and profile target altimate-code#1734); a bashRewrite handler in the shared tool chain inserts the flags for each dbt invocation (dbt build -s x, cd a && dbt run, uv run dbt test) that does not already carry --defer, --no-defer, --state, DBT_STATE and so on. deps, clean, debug, init, retry, docs and source are left alone.
  • /defer [status|on|off|reset] shows or overrides the setting for the session; /defer on says why when no usable state directory is configured.
  • /target [<name>|reset] sets a session target; the rewrite adds --target <name> when it differs from the profile's default and the command names none. Names are checked against the profile's outputs.
  • The status line part shows target and defer, for example dbt dev · defer prod.
  • DeferState in types/index.d.ts.

Remote defer mode is reported by the tool as not supported yet, so it never rewrites commands.

The branch includes the foundation commit; retarget once the foundation PR merges. Merge after the altimate-code PR, since the plugin calls the CLI tool.

Known limits

  • The shell reading is lexical: a command with a folder change or project option it cannot follow is left as written (defer does not apply), never rewritten for the wrong project.
  • The project check starts from the session folder (the engine exposes no shell folder), and a nested dbt_project.yml or symlinked folder below the project is treated as the project.
  • cd tracking duplicates a smaller version in lineage.tsx; sharing it is a follow-up.

Demo video

Testing

  • claude plugin test ./plugins/altimate-code: 233 pass, including hooks/features/defer.test.ts (rewrite of dbt build -s x, cd a && dbt run, uv run dbt test; no rewrite with --state present or defer off; /defer and /target; through-the-plugin rewrite).
  • claude plugin validate --strict . passes. --strict ./plugins/altimate-code fails on warnings that the foundation commit already has (the existing lineage test file and the missing icon); this change adds none that fail.
  • bash tests/*.sh all pass.

Demo video (hosted)

P-04.mp4 — watch on Notion (Altimate workspace; recorded from the approved head of this PR).

🤖 Generated with Claude Code

hkaltai and others added 7 commits November 13, 2026 16:31
Each feature gets its own file under hooks/features/, called by name from
features/index.ts in a fixed order: its own hooks, the session and turn
events, its band line and its tool-call phases. One tool.call hook
(tool-chain.ts) runs Bash and file handling in fixed phases: bashRewrite,
bashGate, the call, bashAfter, editAfter, readOrEditAfter. The status line
is built from parts (status-line.ts). runTool moves to altimate-cli.ts with
a `write` option that goes through the CLI with --allow-write.
dbt-command.ts finds the dbt invocations in a shell command line. New
userConfig fields: maxScanBytes, healthBlocksPush, healthConfigPath,
commentsPollSeconds, commentsInContext.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…r and /target

Claude's dbt commands get --defer --state <dir> (and --favor-state) right after
the subcommand when the project's Power User defer setting is on, unless the
command already sets them. /defer status|on|off|reset and /target <name> change
this for the session; the status line shows the target and defer state.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Subshells after keywords, case patterns, process substitution, arrays,
arithmetic and function definitions parse again; quotes in a heredoc inside
a substitution are text; a function or case pattern named dbt is not an
invocation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ps old dbt's skip list, and survives a new session

The rewrite checks where the command runs (cd, pushd, --project-dir,
DBT_PROJECT_DIR, Windows paths); deps, clean, debug, init, docs, source and
retry get no --defer; a new session clears the status part; a failed read is
tried again after a minute; the read in flight is owned by its own session.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…anges and exports it cannot follow, and keeps /defer reset from overwriting a newer session

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@hkaltai

hkaltai commented Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

Review round 1 (independent claude -p and codex exec reviewers, three attack-the-fix gate runs). Replies per finding — fixes are in ce3f002.

# Finding Reviewer Resolution
1 A project named with --project-dir / DBT_PROJECT_DIR anywhere in the line vouched for every dbt command in it codex, MAJOR Fixed: only a single dbt command with the option inside its own text is judged; anything else is left as written.
2 Folder changes not followed (popd, env -C/--chdir, command cd, bare cd, $/backtick words, quoted forms like 'cd', "."/..) codex, MAJOR Fixed: such lines are left as written (folder unknown). Tests added.
3 Descendant folder judged the same project without checking a nested dbt_project.yml / symlink codex, MAJOR Not changed: needs filesystem access inside a pure function; the case is a nested project inside the one being worked in. Recorded as a known limit.
4 /defer reset could publish a read from an earlier session codex, MAJOR Fixed: the same generation check ensure uses. Checked by the gate with an in-memory race run; not a durable test (the test harness cannot hold a CLI call).
5 --target between a command group and its subcommand (dbt source --target x freshness) claude, MAJOR (0.8) Rebutted with evidence: with the installed dbt 1.10, dbt docs --target x generate and dbt source --target x freshness are accepted, while dbt docs --bogus generate is rejected, so group-level --target is valid.
6 NO_DEFER skip list lets --defer reach parse / run-operation claude, MAJOR (0.6) Rebutted with evidence: installed dbt 1.10 lists --defer for parse and run-operation. Skip list kept for commands that read or write run state.
7 Project check starts from the session root, not the shell's current folder claude, MAJOR (0.55) The engine exposes no shell folder; recorded as a known limit, left in the description.
8 cd tracking duplicates lineage.tsx claude, MAJOR (0.6) lineage.tsx belongs to another change; sharing the helper is a follow-up.
9 /target <name> claims success with no dbt project claude, MINOR Fixed.
10 Rewrites wrong when invocations are not in source order (dbt ls <(dbt ls)) claude, MINOR Fixed: sorted by position; test added.
11 export DBT_STATE=… && dbt build overridden claude, MINOR Fixed: a line with an export of DBT_STATE / DBT_TARGET is left alone, whatever the quoting. Tests added.
12 First read can hold the first dbt command up to 60 s claude, MINOR Not changed: a CLI that does not answer is retried only once a minute; a shorter timeout needs an engine option I could not confirm.
13 Redundant DBT_TARGET= check claude, NIT Kept: the parser's target does not cover an export.

Attack-the-fix gates: run 1 found residual gaps (fixed), run 2 found quoted-word bypasses (fixed), run 3 found three more quoting cases (fixed in the last commit; not re-gated because the gate cap is two re-runs). The lexical shell reading here is a heuristic: where it cannot tell, it leaves the command as written, and a skipped rewrite means defer does not apply, never a wrong one.

claude plugin test: 233 pass.

…this one, and DBT_DEFER settings of the user

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@hkaltai

hkaltai commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Final review round (claude -p and codex exec, fresh processes). Fixed in a74e10c: a cd inside a subshell or backticks now skips the rewrite; --project-dir must name this project exactly (a folder below it may be its own project); DBT_DEFER / DBT_DEFER_STATE / DBT_FAVOR_STATE set inline or exported are treated as the user's own choice. Tests added. Not changed: --target between a group word and its subcommand (dbt source/docs) is accepted by dbt 1.10 (checked against the installed CLI); the shell's carried folder versus the session root is a known limit of the line reading, where it cannot tell it skips. These fixes were not re-gated, so the PR stays draft.

@hkaltai
hkaltai marked this pull request as ready for review November 14, 2026 05:44
@hkaltai

hkaltai commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

review-loop: APPROVED at a74e10c

}))
const state = await started
// Another session's read must not be dropped by a caller that was waiting on this one.
if (loading === started) loading = null

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[WARNING]: A rejected shared read is never cleared, so defer dies silently for the rest of the session.

started is stored in loading before it settles. If load() rejects, or publish inside the .then rejects, await started throws here and this line never runs, so loading keeps the rejected promise; every later ensure() reuses it through ??= and rejects again. featuresBashRewrite swallows that error (features/index.ts:242), so no dbt command is rewritten and /defer//target fail until the next session.start. This is reachable when a $ call on a session that is going away throws (the same engine-gone case altimate-cli.ts:38-41 documents), or when the status-line update fails. Clear loading in a finally, and cover the rejection path in defer.test.ts (the existing retry test only covers a returned failure).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 970e648: ensure() now clears loading in a finally, so a rejected shared read is not reused by later calls (defer.tsx, ensure). I could not add a harness test for it: the test engine swallows a throwing process.run or ui.status handler inside runCli/setStatusPart, so the rejection never reaches ensure() from a test. The existing retry test still covers the returned-failure path.

const first = [...invocations].sort((a, b) => a.start - b.start)[0]
const project = resolvePath(projectDir, '.')
if (!first || !project) return false
const inside = (dir: string | null) => !!dir && (dir === project || dir.startsWith(`${project.replace(/\/+$/, '')}/`))

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[WARNING]: inside() also accepts a folder below the project, so a cd into a nested dbt project still gets this project's --defer --state (and the session --target).

runsInProject('cd analytics && dbt run', '/repo', '/repo') returns true even when /repo/analytics/dbt_project.yml exists, so dbt runs the nested project against /repo's production state directory. That contradicts the function's own goal (never rewrite for the wrong project) and is inconsistent with the exact-match rule added for --project-dir at line 154 with the rationale that a folder below it may be a separate dbt project. Check the effective project from dir (for example $.fs.exists(dir + '/dbt_project.yml') in bashRewrite, where $ is available) or require dir === project here too.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Declined for this PR. cd models && dbt run into a folder below the project is deliberately rewritten and tested (defer.test.ts 'cd models && dbt run'), and telling that apart from a nested dbt project needs a filesystem check that the pure runsInProject does not have. A dbt project nested inside another is not a layout this feature supports; the exact-match rule for --project-dir stays because there the user names the folder outright. Noted as a known limit.

await publish($, state)
return { text: `Defer cannot be turned on: ${state.reason ?? 'no state directory is configured for this project (dbt.deferConfigPerProject).'}` }
}
state = { ...state, override: word === 'on' }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: /defer on|off (and /target <name> at line 296) publish after an awaited ensure() without the generation guard that /defer reset uses at lines 268-271. If the session restarts while that settings read is in flight (/clear, resume), the old handler resumes and writes its override/target into the new session's atom and status line, contradicting the 'for this session' promise. Capture generation before ensure() and skip publish when it changed, the same way reset does.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 970e648: /defer on|off and /target <name> capture generation before ensure() and skip publish when the session restarted meanwhile, as reset does.

targets?: string[]
}

const dirname = (path: string) => path.replace(/[\\/]+[^\\/]*$/, '') || '/'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: This dirname duplicates lineage.tsx:169 but behaves differently (dirname('/repo') is '/' here and '/repo' there), and findProject also duplicates the upward walk and downward scan of projectRoot/projectsBelow (lineage.tsx:173-225, which additionally skips SKIP_DIRS and caches). The copies have already diverged: the CD regex here follows if cd x; then dbt run; fi while the lineage one does not, so /lineage and /defer can resolve the same command to different folders/projects. The PR lists sharing this helper as a follow-up; doing it now prevents further drift.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Declined for this PR; the PR description lists sharing the lineage helpers as a follow-up. The two dirname/findProject copies differ on purpose in small ways (root handling, the if cd x; then form) and merging them touches lineage.tsx and its tests, which this change should not.

* folder (`cd`, `pushd`, `--project-dir`, `DBT_PROJECT_DIR`, uv's `--directory`) or one it cannot work out.
*/
export function runsInProject(command: string, root: string, projectDir: string): boolean {
if (/\s--(?:directory|project)[\s=]/.test(command)) return false

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: The --directory/--project guard reads the raw line, so a quoted flag slips past it: uv run "--directory=../b" dbt run does not match this regex (a quote follows the space, not --), while parseDbtCommand still finds the dbt run after the quoted launcher option, and the command is rewritten with this project's --defer --state even though uv runs dbt in ../b. The rest of the function deliberately checks the quote-stripped plain copy for exactly this class of bypass; run this check against plain too (or read --directory from the parsed invocation).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 970e648: the --directory/--project check now also runs on the quote-stripped copy, so uv run "--directory=../b" dbt run is not rewritten. Test: 'a quoted --directory or --project option is not followed'.

export async function bashRewrite($: EngineInterface, e: BashCall): Promise<string | null> {
// Most commands name no dbt: they never cost the settings read.
if (!/\bdbt\b/.test(e.command)) return null
const state = await ensure($)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: Any command that merely contains the word dbt triggers the settings read before the parser confirms an invocation. cat dbt_project.yml, grep -rn dbt models/ and git commit -m "dbt" all call ensure() and, on the first one in a session, wait up to the 60 s CLI timeout for dbt_defer_state (cliOnly) even though rewriteDeferCommand would return the command unchanged. parseDbtCommand is already imported; return null when it finds no invocation, and only then read the setting.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 970e648: bashRewrite returns null before the settings read unless parseDbtCommand finds an invocation, so cat dbt_project.yml and git commit -m "dbt" never read. Test: 'a command that only mentions dbt does not read the setting'.

if (entry.kind !== 'dir' || entry.name.startsWith('.') || entry.name === 'node_modules') continue
if (await $.fs.exists(`${root}/${entry.name}/dbt_project.yml`).catch(() => false)) below.push(`${root}/${entry.name}`)
}
return below.length === 1 ? below[0]! : null

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: With two dbt projects directly under the session root (a common monorepo layout), findProject returns null, bashRewrite bails on !state.projectDir (line 331), so even cd dbt_a && dbt build gets no defer and /target answers 'No dbt project found' (line 295) for the whole session. runsInProject could judge that command if the project were resolved from its cd/--project-dir. Either resolve the project per command when there is more than one, or state this limit alongside the other known limits.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Declined as a behavior change. With two projects directly under the session root there is no single project to read settings for, and picking per command would need a new resolution rule (and a read per project). /target already says 'No dbt project found' in that case. I will note it as a known limit in the description.

if (next) {
await update($, status, () => next)
showStatusLine($, next)
await showStatusLine($, next)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: refresh checks mine !== latestRefresh at line 104, then awaits update(status) and now this async showStatusLine (which itself awaits update and read inside setStatusPart). A refresh that passes the check can be suspended while a newer refresh runs to completion, then resume and overwrite the newer status atom/status-line part with its stale counts. Re-check mine !== latestRefresh right before showStatusLine (the previous synchronous $.ui.status call left no such window).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 970e648: refresh re-checks mine !== latestRefresh right before showStatusLine, after the awaited update (integrations.tsx). No separate test: the harness has no way to interleave two in-flight status reads at that point.

@kilo-code-bot

kilo-code-bot Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: 4 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 3
Issue Details (click to expand)

WARNING

File Line Issue
plugins/altimate-code/hooks/features/defer.tsx 132 inside() accepts folders below the project, so cd analytics && dbt run into a nested dbt project still gets this project's --defer --state and session --target (inconsistent with the exact-match rule at line 154).

SUGGESTION

File Line Issue
plugins/altimate-code/hooks/features/defer.tsx 72 dirname/project discovery duplicate lineage.tsx and have already diverged (dirname('/repo'), CD regex), so /lineage and /defer can resolve the same command differently.
plugins/altimate-code/hooks/features/defer.tsx 89 Two dbt projects under the session root make projectDir null, so no command is rewritten and /target reports no project, even for cd dbt_a && dbt build.
plugins/altimate-code/hooks/features/defer.tsx 121 The raw-line --directory/--project test is subsumed by the new plain test (quotes and backslashes are the only characters removed), so command need not be tested twice.
Files Reviewed (3 files changed in 970e648; 21 files in the PR)
  • plugins/altimate-code/hooks/features/defer.tsx - 4 issues (3 carried forward, 1 new); the rejected-read finally, the generation guards on /defer on|off and /target, the plain quote bypass, and the parseDbtCommand pre-check are verified fixed
  • plugins/altimate-code/hooks/features/defer.test.ts - no issues; new cases match the harness (reads, quoted --directory) and the parser behavior
  • plugins/altimate-code/hooks/integrations.tsx - no issues; the new latestRefresh re-check before showStatusLine closes the stale status-line write

Fix these issues in Kilo Cloud

Previous Review Summary (commit a74e10c)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit a74e10c)

Status: 8 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 2
SUGGESTION 6
Issue Details (click to expand)

WARNING

File Line Issue
plugins/altimate-code/hooks/features/defer.tsx 229 A rejected shared settings read stays cached in loading; every later ensure() reuses the rejected promise, so defer silently stops and /defer//target fail for the rest of the session.
plugins/altimate-code/hooks/features/defer.tsx 132 inside() accepts folders below the project, so cd analytics && dbt run into a nested dbt project still gets this project's --defer --state and session --target (inconsistent with the exact-match rule at line 154).

SUGGESTION

File Line Issue
plugins/altimate-code/hooks/features/defer.tsx 263 `/defer on
plugins/altimate-code/hooks/features/defer.tsx 72 dirname/project discovery duplicate lineage.tsx and have already diverged (dirname('/repo'), CD regex), so /lineage and /defer can resolve the same command differently.
plugins/altimate-code/hooks/features/defer.tsx 118 The --directory/--project guard reads the raw line; uv run "--directory=../b" dbt run bypasses it and is rewritten with the wrong project's state.
plugins/altimate-code/hooks/features/defer.tsx 330 Any command containing the word dbt (cat dbt_project.yml, grep dbt …) triggers the up-to-60 s settings read before parseDbtCommand confirms an invocation.
plugins/altimate-code/hooks/features/defer.tsx 89 Two dbt projects under the session root make projectDir null, so no command is rewritten and /target reports no project, even for cd dbt_a && dbt build.
plugins/altimate-code/hooks/integrations.tsx 108 Awaiting the now-async showStatusLine after the latestRefresh check widens the stale-refresh window, letting an older refresh overwrite newer status counts.
Files Reviewed (21 files)
  • plugins/altimate-code/.claude-plugin/plugin.json - no issues
  • plugins/altimate-code/hooks/altimate-cli.ts - no new issues (runTool moved from lineage.tsx unchanged apart from the write option)
  • plugins/altimate-code/hooks/dbt-command.test.ts - no issues; parser edge cases (heredocs, case, subshells, process substitution, joined short flags) checked and covered
  • plugins/altimate-code/hooks/dbt-command.ts - no issues found in the lexer/readable/offset logic
  • plugins/altimate-code/hooks/features/comments.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/cost.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/cte-profile.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/defer.test.ts - no issues (rejection path untested; see WARNING at line 229)
  • plugins/altimate-code/hooks/features/defer.tsx - 6 issues
  • plugins/altimate-code/hooks/features/docs.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/health.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/index.ts - no issues
  • plugins/altimate-code/hooks/features/runs.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/sql-graph.tsx - stub, no issues
  • plugins/altimate-code/hooks/features/to-model.tsx - stub, no issues
  • plugins/altimate-code/hooks/integrations.tsx - 1 issue
  • plugins/altimate-code/hooks/lineage.tsx - refactor only, hook wiring checked, no issues
  • plugins/altimate-code/hooks/status-line.ts - no issues
  • plugins/altimate-code/hooks/tool-chain.test.ts - no issues
  • plugins/altimate-code/hooks/tool-chain.ts - no issues
  • plugins/altimate-code/types/index.d.ts - no issues

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 66.5K · Output: 15.6K · Cached: 508.7K

…llowed, only real dbt invocations read the setting, /defer and /target skip a restarted session, stale status refresh is dropped

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
// A folder change this does not follow (`popd`, `env -C`, `command cd`, a `cd` with no folder) leaves the folder unknown.
// Quotes and backslashes are dropped for this check: `command 'cd' ../b` and `env "-C" ../b` change folder like their plain forms.
const plain = command.replace(/["'\\]/g, '')
if (/\s--(?:directory|project)[\s=]/.test(command) || /\s--(?:directory|project)[\s=]/.test(plain)) return false

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SUGGESTION]: The raw-line test is redundant: plain is command with only quotes and backslashes removed, and this pattern's characters (whitespace, -, letters, =) are never among them, so every match in command is also a match in plain. The new plain check alone covers both the quoted and unquoted forms:

Suggested change
if (/\s--(?:directory|project)[\s=]/.test(command) || /\s--(?:directory|project)[\s=]/.test(plain)) return false
if (/\s--(?:directory|project)[\s=]/.test(plain)) return false

@hkaltai

hkaltai commented Nov 15, 2026

Copy link
Copy Markdown
Contributor Author

review-loop: APPROVED at 970e648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant