Question 570
A project contains many large prompt-evaluation datasets inside the same Git repository, inflating clone times. What should be separated?
Explanation
Correct Answer
Git tracks prompt source effectively; external governed data versioning handles bulky test corpora more safely.
Incorrect Answers
Create an approved release tag for the exact prompt commit. That operation would be relevant if: The organization wants a traceable release named prompts-v2.4 across several services. Its corresponding reason or verification is: A protected tag can identify the immutable prompt revision all consumers should deploy and audit. However the problem in this question is: A project contains many large prompt-evaluation datasets inside the same Git repository, inflating clone times. The requirement instead calls for Keep large governed evaluation datasets in versioned storage and reference them from Git metadata; the question-specific check is: Git tracks prompt source effectively; external governed data versioning handles bulky test corpora more safely.
Pin workflow actions to reviewed commit SHAs and minimize token scopes. A separate source case supports that approach when: An automatic prompt deployment downloads actions from unpinned third-party GitHub repositories with broad token permissions. The supporting rationale or observable result is: Reproducible dependencies and least privilege reduce the chance that automation changes unexpectedly during a sensitive release. This question describes a different issue: A project contains many large prompt-evaluation datasets inside the same Git repository, inflating clone times. Address it through Keep large governed evaluation datasets in versioned storage and reference them from Git metadata, with the required justification or evidence: Git tracks prompt source effectively; external governed data versioning handles bulky test corpora more safely.
Record and deploy the exact prompt Git commit SHA or immutable release tag. This is useful for the distinct issue: A deployed prompt is referenced as main branch latest, and reviewers cannot reproduce yesterday's responses. The relevant technical rationale or evidence for that issue is: Immutable revisions identify the instructions used by each release independently of subsequent branch changes. Here the reported issue is: A project contains many large prompt-evaluation datasets inside the same Git repository, inflating clone times. The relevant response is: Keep large governed evaluation datasets in versioned storage and reference them from Git metadata. The first result cannot verify this different correction: Git tracks prompt source effectively; external governed data versioning handles bulky test corpora more safely.