Skip to content

SND repo migration history #926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
labkey-martyp merged 1 commit into from
May 7, 2026
+30 −0
Merged

SND repo migration history #926

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions snd/history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# snd module history

**TL;DR:** the `snd` module's full commit history travels with it on every migration. **File-level** history and blame work everywhere — GitHub, IntelliJ, and any tool that follows renames (Sourcetree, GitKraken, Fork, GitLens, `git log --follow`, etc.). **Directory-level** history (`git log -- snd/` or GitHub's directory tree view) only shows commits since the most recent migration — for older directory-level browsing, open the corresponding repo from the table below.

## Why directory-level history is limited

Each migration changed the path of the module — first from a repo root into a subdirectory, then between subdirectories. Git's rename detection is per-file, not per-directory, so a directory-level log starts fresh at each move even though every individual file's history remains intact.

## Where prior history lives

| Repository | History active | Notes |
|------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------------------------------------------|
| [LabKey/snd](https://github.com/LabKey/snd) | until 2025-02-24 | Original standalone repo. Now archived. |
| [LabKey/ehrModules/snd](https://github.com/LabKey/ehrModules/tree/fc811d93c1a99ee46e219508da17041a9bcfb2d4/snd) | 2025-02-24 → 2026-05-05 | Rehomed via `LabKey/ehrModules` commit `76b86bc5` ("Rehome snd module"). |
| [LabKey/snprcEHRModules/snd](https://github.com/LabKey/snprcEHRModules/tree/develop/snd) | 2026-05-05 → present | Current home. Rehomed from `LabKey/ehrModules`. |

## Browsing history

### File-level (works everywhere)

Any Git tool that follows renames will show full history back to the module's origin:

- **GitHub**: open any individual file, then click *History* or *Blame*. GitHub follows renames automatically across migrations.
- **IntelliJ**: right-click a file → *Git → Show History* (or *Annotate* for blame).
- **Other tools** (Sourcetree, GitKraken, Fork, GitLens, etc.): use the file's history or blame view — these tools follow renames by default.
- **CLI**: `git log --follow -- <path/to/file>`.

### Directory-level (use the table above)

There is no built-in equivalent to `--follow` for directories. To see directory-level history from before a migration, open the corresponding repo from the table above for the date range you care about and browse the module directory there.
Loading