個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Visualizations of data usage across the archive.
When deploying a fork that points at a different data repository, update the
BASE_URL constant near the top of src/plots.js:檢視完整 README ↗Visualizations of data usage across the archive.
Main webpage: https://usage.dandiarchive.org
When deploying a fork that points at a different data repository, update the
BASE_URL constant near the top of src/plots.js:
const BASE_URL = "https://raw.githubusercontent.com/myorg/myrepo/main";
npm install
npm run dev
npm test # unit tests (Vitest, in jsdom)
npm run test:coverage # the same, with a coverage report
npm run test:e2e # integration tests (Playwright, in Chromium)
npm run test:visual # screenshot comparison of the map against committed baselines
The unit tests cover the page's entry module (src/plots.ts) as well as its
helpers: tests/unit/plots-harness.ts loads the page's markup into jsdom,
stands in for Plotly and for the network, and drives the page through its
controls. Coverage from both the unit and the integration tests is reported
to Codecov; to see what the integration tests exercise in the browser, run
npm run test:e2e:coverage and then npm run coverage:integration.
by_region.tsv, and how to regenerate the table it reads them
with.