Repository navigation
Update from project-template v0.106.0 - #229
Conversation
There was a problem hiding this comment.
🤖 NCode Review at c5f4604: 1 new finding on the changed lines.
|
Superseded by the review at d897c23. |
|
/review |
🤖 Review completeVerdict: ✅ Approve — Re-review of what changed since the last review at c5f4604: 1 hunk in 1 file and changes taken back in 1 file, by correctness only. Earlier findings: F1 fixed. No further findings above nits. 1 reviewer run — 0 findings (run details)
Trial: findings are posted as review threads and in the check run. $0.03 on Amazon Bedrock, 10s, at d897c23. (how to interact) 📋 OutcomesMerged at d897c23: 1 fixed, 0 dismissed, 0 acknowledged, 0 ignored.
|
|
Autopilot: this pull request is ready to merge as far as this run can tell.
Still unresolved, for you to resolve before the merge as the ruleset requires: #229 (comment) After the merge, run the template's |
Moves the project from project-template v0.103.1 to v0.106.0. The update refreshes the template-owned workflow commands, prompts, skills, scripts and decision records, and adds the template's ADR-0032: a plan gets a
Release:line only when it changes what a release ships.AGENTS.mdtakes the template's ADR-0032 sentence..github/workflows/code-review.ymlpasses NCode Review'sapprove: true, as the update's note asks, so a clean review approves the pull request; the v1.4.2 pin and the outcomes job are unchanged.## [Unreleased]records both changes. Nothing is released.After merging, run the template's
tools/Set-RepositoryBaseline.ps1again so the default branch requires NCode Review's approval.