You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2020. It is now read-only.
Currently test images are stored in the git repository. These files won't change much so we should try to save bandwidth and separate concerns by tracking them with git-lfs instead.
Expected Behavior
DICOM images in tests/assets are managed with git-lfs
Acceptance criteria
test images are managed by git-lfs
large image files are removed from the repository
NOTE: All PRs must follow the standard PR checklist.
The text was updated successfully, but these errors were encountered:
I have a public fork here and want to tackle this issue. I can't update my fork with the LFS data because of this issue
Git LFS: (0 of 534 files) 0 B / 268.10 MB
batch response: @poppingtonic can not upload new objects to public fork poppingtonic/concept-to-clinic
batch response: @poppingtonic can not upload new objects to public fork poppingtonic/concept-to-clinic
batch response: @poppingtonic can not upload new objects to public fork poppingtonic/concept-to-clinic
batch response: @poppingtonic can not upload new objects to public fork poppingtonic/concept-to-clinic
batch response: @poppingtonic can not upload new objects to public fork poppingtonic/concept-to-clinic
batch response: @poppingtonic can not upload new objects to public fork poppingtonic/concept-to-clinic
@poppingtonic Hey, thanks for jumping in :) I think what would be the best "next step" would be if you could get a branch / PR up and running here - that way it should smooth the permissions out, no?
@poppingtonic Thanks so much for this. As we can't work around the permissions I've gone ahead and done this in 7d46f08 and will credit you for the effort :)
Add make command to generate html files
Add docker services for document generation
Add dependencies for sphinx in prediction reqs
This is because I build the documentation container from the prediction
development Dockerfile.
Make command to run tests on documentation service
Add documentation table of content
Restart document compiling always
Add how to edit this documentation file
Add testing of the docs and more instructions
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview
Currently test images are stored in the git repository. These files won't change much so we should try to save bandwidth and separate concerns by tracking them with
git-lfs
instead.Expected Behavior
DICOM images in
tests/assets
are managed withgit-lfs
Acceptance criteria
git-lfs
NOTE: All PRs must follow the standard PR checklist.
The text was updated successfully, but these errors were encountered: