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
Given ALMA decided to move away from Subversion, they created a new git repository, which may be incompatible with our current ALMA git repository.
Having that in mind we should consider the following options:
To keep the current repository and try to align it with the new ALMA ACS repository.
Freeze the current repo, and start a new one with compatibility with LFS and also compatible with new git ALMA ACS repository.
I am inclined for the second option.
I would like to hear from the other participants before take a desicion.
The second option is the optimal one in my opinion, because the ACS repository have lots of big tar files, so its better to have a LFS compatible repository.
Im trying to make the merge with ACS-2017DEC from ALMA's public repository in my fork.
The main issue is that Github doesn't allow to add new lfs files into a public fork
Looking in some git-lfs issues, the original repository (this one), has to have the git lfs content
git-lfs/git-lfs#908 (comment)
The text was updated successfully, but these errors were encountered: