Conversation
The input caches kapi's parse cache, which has nothing to do with content memory. cache-tm stays as a deprecated alias: when a workflow sets it, it decides and the action prints a warning naming parse-cache. One step resolves the value and both conditions read it. The input description and the README now describe kapi 1.3: the project's context lives in kapi's workspace and moves through a context backend with kapi context pull, which this action leaves to kapi-action's context-sync input or the workflow's own step. The test workflow covers parse-cache: false, cache-tm: false, and cache-tm deciding over parse-cache. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PWc9qYQJ93y88XrN6TkMvT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The input carries kapi's parse cache (
.kapi/work/cache/docs), which has nothing to do with content memory, so it is nowparse-cache.cache-tmkeeps working as a deprecated alias: when it is set it decides, and the action prints a warning naming the new input. One step computes the effective value; a new matrix job coversparse-cache: false,cache-tm: false, andcache-tm: trueoverridingparse-cache: false.The input description and README now describe kapi 1.3: project context lives outside git and is fetched with
kapi context pull(kapi-action'scontext-syncinput or your own step), and.kapi/is a cache. The claim that content memory, terms and the unit-state record are committed under.kapi/is removed.Release as v1.6.0 and move
v1before kapi-action v1.7.0, whose README namesparse-cache.🤖 Generated with Claude Code