CLAUDE.md@testsA
CLAUDE.md@tests from databricks/unity-gateway is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.
mdr add databricks/unity-gateway/tests/CLAUDE.md@git:20260917.7b439c1Pins git:20260917.7b439c1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- CLAUDE.md file
- Repository
- databricks/unity-gateway
- Path
tests/CLAUDE.md- Versions recorded
- 2
- Latest version
- git:20260917.7b439c1, committed Sep 17, 2026
- First version recorded
- Sep 14, 2026
- Size
- 1,236 bytes
- Repository stars
- 116
- License
- a license file GitHub does not identify
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Test instructions for Claude Code Read and follow [AGENTS.md](AGENTS.md) in this directory and the coverage matrix in [README.md](README.md) before changing tests. Those are the shared instructions for adding, modifying and removing tests; do not maintain a different policy here. In particular, `integration/` uses the real installed ug CLI, selected real agent versions, and the real e2e workspace. No mocks, monkeypatching, internal application calls, fake binaries/services, fabricated ug state, or test-only production behavior. Do not hide failures with skips, xfails, retries or weaker assertions. Update the matrix when coverage changes and distinguish automated coverage from gaps and checks that were not executed. The one carve-out is the `managed_fixture` marker: those tests inject the admin CodingAgentConfig through the built-in `UCODE_MANAGED_CONFIG_STUB` hook so the real `ug configure` path can be exercised across managed-config shapes the live workspace does not publish. That controls only the admin-authored INPUT; the gateway, agent binaries, ug internals, and ug state stay real, and the config fetch/wire contract itself stays covered …
Read the whole file at its exact version.
How to install
mdr add databricks/unity-gateway/tests/CLAUDE.md@sha256:419b713b837a07c4The line at the top of this page pins the label git:20260917.7b439c1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_n2n7exnfiektdsef)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 14, 2026 and Sep 17, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260917.7b439c1 latest | 2026-09-17 | 7b439c1 | 1,236 B | A | view · diff |
| git:20260914.e65ffb4 | 2026-09-14 | e65ffb4 | 729 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1236 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
databricks/unity-gateway · 116 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n2n7exnfiektdsef GET https://markdownregistry.com/api/v1/resolve?ref=databricks/unity-gateway/tests/CLAUDE.md GET https://markdownregistry.com/api/v1/blob/419b713b837a07c4c0273c7f5683de3d4d12f110af49704014e2a36f1945c248
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: what a CLAUDE.md file is · keeping AGENTS.md and CLAUDE.md in sync · which agent file does what.
More from databricks/unity-gateway
Every file in databricks/unity-gateway