Repository navigation
v1.0.1
Immutable
release. Only release title and notes can be modified.
Added
CONTRIBUTING.md,SECURITY.mdanddocs/, with the project template's decision records indocs/decisions/project-template/; the README links them.
Changed
- This repository's own workflow and the README's examples pin v1.0.0.
- The caller runs a plain
/reviewonly on an open pull request, so a/reviewon a pull request that just closed can't cancel or displace the outcomes job in their shared concurrency group;/review explainand/review teachstill answer on a closed one. - The README's
sensitive:example shows NCodeGroup/Identity's real project paths and the set it uses: tokens, keys and secrets, authentication, client and server. - A finding on a repository's
/audit-conventionscommand, prompt file or skill, which project-template generates from v0.45.0, moves upstream to NCodeGroup/project-template like a finding on the template's other generated files. - The repository follows project-template v0.53.0 (from v0.41.1): CI also checks the decision index and the pull request's title and description for agent attribution, and cancels a run a newer push supersedes; Dependabot waits three days before offering a new version and gives security updates and NCode Review bumps pull requests of their own; a workflow auto-merges a Dependabot bump of this repository's own NCode Review pin to a minor or patch release; the Copilot cloud agent's runner is set up as CI is; and agents get the
/address-feedbackand/audit-conventionscommands.
Fixed
- The context, selection and synthesis calls no longer cache their prompts: each makes one request, so caching paid 25% more to write about 150,000 tokens a review that nothing read. Reviewer followers keep reading their leader's cache, as the traces confirmed (#133).
- In a pull request that adopts or updates project-template, a finding on a file the template added through v0.54.0 and replaces on every update moves upstream to NCodeGroup/project-template like a finding on its other files, instead of being posted as the project's: its decision records in
docs/decisions/project-template/, itstemplate-update.ymlandcode-review-auto-merge.ymlworkflows, its C# test rules (.github/instructions/csharp-tests.instructions.mdand.claude/rules/csharp-tests.md) and its .NETbuild/files (ProjectTemplate.globalconfig,ProjectTemplate.Tests.globalconfig,BannedSymbols.txt,dod.ps1andUpdate-PublicApi.ps1) (#148). - A finding that repeats one of the bot's earlier threads on the pull request, posted or dismissed, is listed apart under "Already raised" in the summary comment and the check run, naming the earlier finding, linking its thread and saying "dismissed" when the maintainer dismissed it, and is left out of the finding counts and the annotations; a dismissed one is left out of the verdict too. Before, when every finding repeated a thread, no review was posted, yet the summary comment and the check run still reported them as new findings (#151).
- A pull request that deletes a C# file in a packed project no longer crashes the review with
Cannot read properties of undefined (reading 'trim')when a removed line is an attribute: the public-surface check looked for the declaration below the attribute before the deleted file's first line (#155). - The check run no longer says it's in shadow mode: its title drops "(shadow mode)" and its summary says, as the summary comment does, that findings are posted as review threads and in the check run; the action's description and the README's opening say the same (#151).