Skip to content

archive handling #1176

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

Merged
merged 3 commits into from
Dec 12, 2023
Merged

archive handling #1176

merged 3 commits into from
Dec 12, 2023

Conversation

Byron
Copy link
Member

@Byron Byron commented Dec 12, 2023

Related to this comment

  • feat: write informative message if archives are ignored due to script change.
  • check all git-lfs managed files into the repository

That way one will not be dependent on git-lfs for what ultimately are 6MB of binary files.
I would even have paid for bandwidth, but it seems wrong that bandwidth resets per month
which would leave a lot unused
Otherwise, they are not links anymore when extracted from archive,
unfortunately.
@Byron Byron merged commit 6c2fa02 into main Dec 12, 2023
@Byron Byron deleted the archive-handling branch December 12, 2023 09:18
EliahKagan added a commit to EliahKagan/gitoxide that referenced this pull request May 8, 2024
This modifies the readme and one source code file to no longer say
that Git LFS is required to get generated archives, because they
are checked in as regular blobs instead these days, ever since
35439de (GitoxideLabs#1176). This may simplfy onboarding since readers are no
longer told they must do anything with `git lfs` to get started.

It also removes the LFS step from a CI test job definition that had
it, for the same reason: the generated archives are no longer
stored in LFS, so the only current expected effects of that step
are to make the job slightly more complicated and very slightly
slower. See also 7b3104d (GitoxideLabs#1360) and c60f270.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant