-
Notifications
You must be signed in to change notification settings - Fork 66
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.
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
migrated lfs tracked files (so these files stored in blob instead of diffed) #2707
Conversation
Signed-off-by: Dzmitry Lahoda <dzmitry@lahoda.pro>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Nix commands for this PRNOTE: You can also run our Nix commands in Docker. See the bottom of this comment. Make sure you have setup the Composable community cache:(you only need to run it once on your machine) nix-shell -p cachix --command "cachix use composable-community" Show all possible apps, shells and packages:
Run the Composable node alone:nix run "github:ComposableFi/composable/414dd4220298e770185b9ed59c16f1d83b263893#composable-node" -L Spin up a local devnet:nix run "github:ComposableFi/composable/414dd4220298e770185b9ed59c16f1d83b263893#devnet" -L --option sandbox relaxed --show-trace Spin up a local XCVM devnet:nix run "github:ComposableFi/composable/414dd4220298e770185b9ed59c16f1d83b263893#devnet-xcvm" -L View the docs:nix run ".#docs-server" Run this without Nix in Docker.docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v nix:/nix -it nixos/nix bash -c "nix-env -iA nixpkgs.cachix && cachix use composable-community && nix run github:ComposableFi/Composable/414dd4220298e770185b9ed59c16f1d83b263893#devnet-dali -L --extra-experimental-features nix-command --extra-experimental-features flakes" NOTE: You can swap |
Visit the preview URL for this PR (updated for commit 414dd42): https://picasso-f0d16--pr2707-dz-lfs-migrate-a7h61hrf.web.app (expires Wed, 21 Dec 2022 11:29:44 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: d4e030ec330173845b1768cd217beee9791d20f1 |
Visit the preview URL for this PR (updated for commit 414dd42): https://pablo-afa5d--pr2707-dz-lfs-migrate-48d7508j.web.app (expires Wed, 21 Dec 2022 11:30:04 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 8ef316967fc7aa470dc109d617260c43c009e4e3 |
Signed-off-by: Dzmitry Lahoda dzmitry@lahoda.pro
Issue
LFS was added and file extensions to LFS, but these file not migrated.
After #2646 it appeared that need #2694 and also better to migrate (idea before was not to force migrate, but ensure all new items in LFS). But seems migration is less noisy.
So this PR is result of running just one command to do migration https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.adoc?utm_source=gitlfs_site&utm_medium=doc_man_migrate_link&utm_campaign=gitlfs . Nothing more.
Why? Because LFS has no history and may be avoided on some checkouts which slows down monorepo degradation.
Checklist
@easteregg or other FE is ok for FE stuff
@cor or @Martin-Kiss are ok for doc stuff
@Dom-Roth 🥇 seems got
lfs detected
label violation first docs(governance): Governance writeup #2630look at docasaurus after it released
look at UI
because most of files (only audit may be not) are from UI or docs